Webhook Events (1.2.0)

Event payloads delivered to your configured webhook endpoint.

These are outgoing events — DeepCredentials sends these to your webhook URL when an event occurs.

Every payload is slim by design: the data field carries only the resource id and the status values relevant to the event. To read claims, captured data, identification details, or any other field, fetch the resource via the documented GET endpoint with your API credential. This guarantees no captured data or PII leaves DeepCredentials over the webhook channel without an authenticated call.

Delivery currently makes one synchronous attempt. A failed attempt is logged and discarded, so callbacks can be missed. Reconcile authoritative state through the documented authenticated B2B GET and list endpoints.

See the Webhooks guide for setup, signature verification, and best practices.