MetaMap's webhooks communicate verification events to your server. Verification events hold data on each metamap merit and each check performed. By listening to these events, you can optimize your users' experience in your application.
The following table describes our webhooks:
|Sent at the beginning of the SDKs flow, when MetaMap is making a new verification record (usually at the upload of the first ID document)
|Sent when the user has uploaded all inputs via SDKs. You can use that webhook to know when to redirect the user after the metamap is complete on your website/App.
|Sent from your MetaMap dashboard manually after updating the user verification information.
|When gov check service is postponed and awaiting until step timeout error according the established databases request timeout.
|Sent once MetaMap is done verifying a user entirely. When you get this webhook, you should GET the 'resource' URL to get the verification data about user.
|Based by base64NOMTimeStamp and is triggered only after
verification_completed when digitalSignature service is finished processing.
|Sent when verification is not completed after 30 minutes. It means that the user probably did not finish the metamap.
|webhook sent after each verification step is completed (liveness, face match, document-reading, alteration-detection, template-matching, watchlist)
Updated 3 months ago