> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # List Webhook Destination Deliveries > Page through every delivery attempt to one webhook destination, newest first, with HTTP status, response time and event type. List Webhook Destination Deliveries API Prompt Copy prompt to clipboard \

\`List the delivery attempts made to one Didit webhook destination through the Management API.

Endpoint:
GET https://verification.didit.me/v3/webhook/destinations/{destination_uuid}/deliveries/

Authentication:
Use the x-api-key header with my Didit API key. A scoped API key needs webhooks: read and decisions: read. A key limited to some workflows or to approved sessions cannot use this endpoint.

Goal:
\- Find the webhooks my endpoint failed to accept, so I can fix the endpoint and resend them.

Path parameter:
\- destination_uuid: the destination uuid from GET /v3/webhook/destinations/.

Query parameters (optional):
\- limit (default 50) and offset for pagination.
\- date_from, date_to: UTC days as YYYY-MM-DD, both inclusive.

Behavior:
\- Newest first. Every attempt is its own entry: the first send of an event, each automatic retry and each resend.
\- Response: { count, next, previous, results }. count is exact up to 100 and reads 100 above that, so follow next until it is null instead of computing pages from count.
\- Entries do not carry the payload. Fetch one with GET /v3/webhook/destinations/{destination_uuid}/deliveries/{delivery_uuid}/ to read the headers and body.

Example call:
curl -X GET "https://verification.didit.me/v3/webhook/destinations/{destination_uuid}/deliveries/?limit=50&date_from=2026-05-01" \
-H "x-api-key: YOUR_API_KEY"

What to read from each result:
\- uuid: the delivery id, for the detail and resend calls.
\- response_status: what my endpoint answered. null means the attempt has not been made yet; 504 is a timeout, 503 a connection failure, 400 a URL Didit refused to call, 404 any other request error; 400 or above is a failure.
\- Delivery records are available for about 30 days.
\- response_time_ms, created_at, webhook_type, status, request_url.
\- session_id: the verification session the event is about, or null for business, user, transaction and other events.

Failure modes:
\- 400: invalid date_from or date_to, date_to earlier than date_from, or limit or offset above 1000000.
\- 401: { "detail": "This API key has expired." }
\- 403: { "detail": "You do not have permission to perform this action." }, { "detail": "This API key has no read access to webhooks." }, { "detail": "This API key has no read access to decisions." }, or the limited-key message.
\- 404: { "detail": "Webhook destination not found." }
\- 429: more than 600 GET requests per minute with this key; wait for Retry-After.

Side effects: none. This is a pure read.

For the full integration shape, see /integration/integration-prompt.`

\
Paste into Deliveries are the attempts Didit made to send a webhook to this destination. Automatic retries follow the [retry policy](/integration/webhooks.md#retry-policy) and each appears as its own entry. To send one again after you fix your endpoint, call [Resend Webhook Destination Delivery](/management-api/webhook/resend-delivery.md). For totals over a period, use [Get Webhook Destination Analytics](/management-api/webhook/destination-analytics.md). ## OpenAPI ````yaml GET /v3/webhook/destinations/{destination_uuid}/deliveries/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: Identity verification API. Authenticate with x-api-key header. servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/webhook/destinations/{destination_uuid}/deliveries/: get: tags: - Webhook summary: List webhook destination deliveries description: >- Page through every delivery attempt to one webhook destination, newest first. The first send of each event, each automatic [retry](https://docs.didit.me/integration/webhooks#retry-policy) and each resend are separate entries. Entries carry the HTTP status and response time but not the payload: fetch one delivery to read its headers and body. `count` is exact up to 100 and reads 100 above that, so follow `next` until it is `null`. Delivery records are available for about 30 days. A scoped API key needs `webhooks: read` and `decisions: read`; a key limited to some workflows or to approved sessions cannot use this endpoint. operationId: list_webhook_destination_deliveries parameters: - name: destination_uuid in: path required: true description: >- UUID of the destination (the `uuid` returned by `GET /v3/webhook/destinations/`). schema: type: string format: uuid example: 11111111-2222-3333-4444-555555555555 - name: limit in: query required: false description: >- Maximum number of deliveries per page. Defaults to 50. A value that is not a positive integer falls back to 50; a value above 1000000 returns `400`. schema: type: integer default: 50 minimum: 1 maximum: 1000000 example: 50 - name: offset in: query required: false description: >- Number of deliveries to skip. Defaults to 0. Prefer following the `next` and `previous` URLs from the response. schema: type: integer maximum: 1000000 minimum: 0 default: 0 example: 0 - name: date_from in: query required: false description: >- First UTC day to include, as `YYYY-MM-DD` (inclusive). Omit to start from the oldest delivery available. `dateFrom` is accepted as an alias. schema: type: string format: date example: '2026-10-01' - name: date_to in: query required: false description: >- Last UTC day to include, as `YYYY-MM-DD` (inclusive). Must not be earlier than `date_from`. `dateTo` is accepted as an alias. schema: type: string format: date example: '2026-10-16' responses: '200': description: One page of deliveries, newest first. content: application/json: schema: type: object required: - count - next - previous - results properties: count: type: integer minimum: 0 description: >- Matching deliveries, exact up to 100 and capped at 100 above that. Use `next` to know whether more pages exist. next: type: string format: uri nullable: true description: Absolute URL of the next page, or `null` on the last page. previous: type: string format: uri nullable: true description: >- Absolute URL of the previous page, or `null` on the first page. results: type: array items: $ref: '#/components/schemas/WebhookDestinationDelivery' examples: Failed delivery, its retry and a queued event: value: count: 3 next: null previous: null results: - uuid: 66666666-7777-8888-9999-000000000003 session_id: null request_url: https://yourapp.com/webhooks/didit response_status: null response_time_ms: null status: APPROVED webhook_type: transaction.created created_at: '2026-10-15T09:23:02.871190Z' - uuid: 66666666-7777-8888-9999-000000000002 session_id: 22222222-3333-4444-5555-666666666666 request_url: https://yourapp.com/webhooks/didit response_status: 200 response_time_ms: 143 status: In Progress webhook_type: status.updated created_at: '2026-10-15T09:22:19.104233Z' - uuid: 66666666-7777-8888-9999-000000000001 session_id: 22222222-3333-4444-5555-666666666666 request_url: https://yourapp.com/webhooks/didit response_status: 503 response_time_ms: 412 status: In Progress webhook_type: status.updated created_at: '2026-10-15T09:21:18.412345Z' '400': description: >- `date_from` or `date_to` is not a `YYYY-MM-DD` date, `date_to` is earlier than `date_from`, or `limit` or `offset` is above 1000000 (that error is a JSON array of messages). content: application/json: examples: Malformed date: value: date_from: - >- Date has wrong format. Use one of these formats instead: YYYY-MM-DD. Reversed range: value: date_to: - date_to must be greater than or equal to date_from. Limit too large: value: - limit must not exceed 1000000. '401': description: >- The API key has expired: it was created with an expiry date that has passed. A missing, invalid or revoked key gets `403`, not `401`. content: application/json: schema: type: object properties: detail: type: string description: Human-readable error message. examples: Expired key: value: detail: This API key has expired. '403': description: >- The request is not allowed. A missing, invalid or revoked `x-api-key` gets `You do not have permission to perform this action.` A scoped key without the access this endpoint needs gets a message naming the missing access, and a key used from outside its IP allowlist gets `This API key can't be used from this IP address.` A key limited to some workflows or to approved sessions gets `This API key only reaches sessions inside its workflow or status limits, so it can't use this endpoint.` content: application/json: schema: type: object properties: detail: type: string description: Human-readable error message. examples: Missing or invalid key: value: detail: You do not have permission to perform this action. Scoped key without webhooks read: value: detail: This API key has no read access to webhooks. Scoped key without decisions read: value: detail: This API key has no read access to decisions. Key limited to workflows or approved sessions: value: detail: >- This API key only reaches sessions inside its workflow or status limits, so it can't use this endpoint. Outside the IP allowlist: value: detail: This API key can't be used from this IP address. '404': description: >- No destination with this UUID exists for the application, or it has been deleted. content: application/json: schema: type: object properties: detail: type: string description: Human-readable error message. examples: Destination not found: value: detail: Webhook destination not found. '429': description: >- Rate limit exceeded: more than 600 GET requests in the current one-minute window for this API key. Wait `Retry-After` seconds before retrying. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 example: 30 X-RateLimit-Limit: description: Requests allowed in the one-minute window (600). schema: type: integer example: 600 X-RateLimit-Remaining: description: Requests left in the current window. schema: type: integer example: 0 X-RateLimit-Reset: description: Unix time (seconds) when the current window resets. schema: type: integer example: 1792056120 X-RateLimit-Scope: description: Name of the budget that was exceeded. schema: type: string example: generic-get content: application/json: schema: type: object properties: detail: type: string description: Human-readable error message. examples: Throttled: value: detail: >- GET request rate limit exceeded. You can make up to 600 requests per minute. security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X GET 'https://verification.didit.me/v3/webhook/destinations/11111111-2222-3333-4444-555555555555/deliveries/?limit=50&date_from=2026-10-01' \ -H 'x-api-key: YOUR_API_KEY' - lang: python label: Python source: >- import os import requests destination_uuid = '11111111-2222-3333-4444-555555555555' url = f'https://verification.didit.me/v3/webhook/destinations/{destination_uuid}/deliveries/' params = {'limit': 50, 'date_from': '2026-10-01'} while url: resp = requests.get( url, headers={'x-api-key': os.environ['DIDIT_API_KEY']}, params=params, timeout=10, ) resp.raise_for_status() page = resp.json() for delivery in page['results']: if delivery['response_status'] is None or delivery['response_status'] >= 400: print(delivery['uuid'], delivery['webhook_type'], delivery['response_status']) url, params = page['next'], None # next already carries the query string - lang: javascript label: JavaScript source: >- const destinationUuid = '11111111-2222-3333-4444-555555555555'; let url = `https://verification.didit.me/v3/webhook/destinations/${destinationUuid}/deliveries/?limit=50&date_from=2026-10-01`; while (url) { const resp = await fetch(url, { headers: { 'x-api-key': process.env.DIDIT_API_KEY } }); if (!resp.ok) throw new Error(`Request failed: ${resp.status}`); const page = await resp.json(); for (const delivery of page.results) { if (delivery.response_status === null || delivery.response_status >= 400) { console.log(delivery.uuid, delivery.webhook_type, delivery.response_status); } } url = page.next; } components: schemas: WebhookDestinationDelivery: type: object description: >- One delivery attempt to a webhook destination. The first send of an event, each automatic retry and each resend are separate deliveries. required: - uuid - session_id - request_url - response_status - response_time_ms - status - webhook_type - created_at properties: uuid: type: string format: uuid description: Delivery ID, for the detail and resend calls. session_id: type: string format: uuid nullable: true description: >- User verification session the event is about. `null` for business session, user, business, transaction, Travel Rule and workflow events. request_url: type: string format: uri nullable: true description: >- URL the delivery was sent to: the destination's URL when the event was generated. response_status: type: integer nullable: true description: >- 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: type: integer nullable: true minimum: 0 description: >- Time the attempt took, in milliseconds. `null` while the delivery is queued. status: type: string nullable: true description: >- 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: $ref: '#/components/schemas/WebhookEvent' created_at: type: string format: date-time description: When the delivery was created. WebhookEvent: type: string description: >- Supported webhook event name. Use these exact strings in `subscribed_events`; unsupported values are rejected. enum: - 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 securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- 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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.