In the response you get the following data:
sessionUUID - varchar255 - is a unique identifier of the new auth session
tokenUUID - varchar255 - a unique security token of the session
channel - varchar255 - you can ignore this, as it shows that no Logintap auth delivery channels, like messengers, exist for the user
warning - varchar255 - should be empty if all is ok, an example would be a notification that your plan is over limit (auth will still happen)
webAuthnState - integer = 1 means the objectUUID user has biometry previously connected; = 0 - no biometry was yet connected
loginURL - varchar255 - an address to send users to VERIFY their biometry. IMPORTANT - If the user has "webAuthnState"=0 you will get back "regURL" instead of "loginURL", to register biometry without looking for the user in DBs, so please make sure you only allow using "regURL" for your known users, out of your secure area. The name change is designed to make sure you notice the difference and allow the "regURL" from secure area only!
loginShortUrl - varchar255 - same as above, for places where you need a short link