#aerologic_docs
cedar kettleBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1267879490835710073
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
warm pecan
Hello
There's no documented delay as such as far as I know..
The best practice here would be to listen to webhook events to get notified about verification results being ready
merry storm
Oh okay. Well currently our webhooks are what receive and update user information in our core system, except for address, because those can become outdated. So we wanted to implement a way to pre-populate this information once they complete document verification and then present it to them to validate/update. So basically the flow would be: User clicks button > Identity verification modal opens > User completes verification > We ping our API to check for results > Display results or move on if taking too long. So that's why I was maybe hoping for an average timeframe to go off of.
warm pecan
Hmm yeah unfortunately, I don't think we have a measure for that with the public APIs.
As an alternative, you can poll the API let's say every 5-10 seconds till status for verification session changes to verified
merry storm
Yeah I think that's the approach we'll have to start with. I suppose a partial implementation is needed so I can test availability times myself. Either way, thanks for the input!