Webhook Overview

the detected platform has 2 webhooks that fire when particular events happen within the platform webhook name description docid\ jv4e a 44hhrn12julnvk triggered by specific events in the verify portal and related to the kyc jouney of an indervidual docid 6qlwfwddkxpsscj192lh triggered by events in the lifecycle of a profile docid\ i4npmbvhvuk pqtzxrlhf triggered by events in the processing of documents such as translate, ocr, fraud check etc enabling webhooks to enable webhooks navigate to the integration information section of the monitoring dashboard select the required webhooks and input the following webhook url = the url that you'd like to recieve the webhook webhook secret = a string used to sign the webhook request webhook verification webhook requests are signed to ensure authenticity each request includes a signature header to verify the webhook generate a signature on your side using the following steps use the sha256 algorithm combine the received json payload with the secret value provided in the dashboard compare your generated signature with the signature header from the webhook request if the signatures match, the webhook is verified successfully webhook timeout and retries webhooks by default are fire and forget detected offers timeout and retries on webhooks as part of enterprise infrastructure, which provides the following if a 2xx status is not recieved timeout 3 seconds retry 2 times (10 seconds apart)