Skip to main content
POST
curl
Each call delivers the webhook again. Make your endpoint idempotent on event_id before you resend in bulk, and resend only deliveries whose response_status is null, 400 or above.
A resend goes to the URL the original delivery used. If you moved the destination to a new URL, the old deliveries still point at the old one. Find the deliveries to resend with List Webhook Destination Deliveries, and see the webhooks guide for signature verification.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Path Parameters

destination_uuid
string<uuid>
required

UUID of the destination the delivery was sent to.

delivery_uuid
string<uuid>
required

UUID of the delivery to resend: the uuid of an entry returned by GET /v3/webhook/destinations/{destination_uuid}/deliveries/.

Response

The new delivery, already attempted. response_status is what your endpoint answered this time (504 timeout, 503 connection failure). The original delivery is unchanged.

One delivery attempt to a webhook destination, with the exact request headers and body Didit sent.

uuid
string<uuid>
required

Delivery ID, for the detail and resend calls.

session_id
string<uuid> | null
required

User verification session the event is about. null for business session, user, business, transaction, Travel Rule and workflow events.

request_url
string<uri> | null
required

URL the delivery was sent to: the destination's URL when the event was generated.

response_status
integer | null
required

HTTP status your endpoint returned. null while the delivery is queued and not yet attempted. When no HTTP answer was received Didit records a status of its own: 504 when your endpoint did not answer within 5 seconds, 503 for a connection failure, 400 when the URL was refused as unsafe (for example a private or internal address), and 404 for any other request error. 400 or above counts as a failed delivery.

response_time_ms
integer | null
required

Time the attempt took, in milliseconds. null while the delivery is queued.

Required range: x >= 0
status
string | null
required

Status the event reported when it was generated: the session status for session events (for example Approved or In Review), the person's or company's status for user and business events, and the transaction status for transaction events. null for events that carry no status.

webhook_type
enum<string>
required

Supported webhook event name. Use these exact strings in subscribed_events; unsupported values are rejected.

Available options:
status.updated,
data.updated,
user.status.updated,
user.data.updated,
business.status.updated,
business.data.updated,
activity.created,
transaction.created,
transaction.status.updated,
travel_rule.status.updated,
workflow.compliance_changed,
auth.signup,
auth.login,
auth.login_failed,
auth.password_reset_requested,
auth.password_reset_completed,
auth.mfa_changed,
auth.new_device,
auth.account_locked,
investigator.report.ready,
investigator.decision.automated,
investigator.decision.overridden,
investigator.decision.contested,
investigator.question.raised,
investigator.automation.paused,
investigator.rfi.answered,
investigator.rfi.overdue,
investigator.drift.detected,
investigator.sla.breached,
investigator.qa.failed,
investigator.external.report.ready
created_at
string<date-time>
required

When the delivery was created.

request_header
string
required

JSON text (a string) of the request headers Didit sent: Content-Type, X-Signature, X-Signature-V2, X-Signature-Simple, X-Timestamp and User-Agent. Parse it with a JSON parser. It holds signatures, never the signing secret.

request_body
string
required

JSON text (a string) of the exact payload Didit sent, keys sorted, including event_id and timestamp. Parse it with a JSON parser; see Payload shape. For a scoped key without media: read, media URLs inside it are null; without sessions: write, session tokens and hosted verification links are null. A body changed that way no longer matches its signatures. Didit does not record the response body your endpoint returned.