> ## Documentation Index > Fetch the complete documentation index at: https://v2.docs.conduit.financial/llms.txt > Use this file to discover all available pages before exploring further. # List webhook deliveries > Returns a paginated list of delivery attempts for the authenticated organization. Optionally filter by `endpointId`, by delivery `status` (`pending`, `processing`, `succeeded`, `failed`), or by `eventType` (exact match, e.g. `transaction.failed`). An unknown `status` value returns 400; an unknown `eventType` returns an empty page. ## OpenAPI ````yaml https://api.sandbox.conduit.financial/v2/api-docs/openapi.json get /webhooks/deliveries openapi: 3.0.0 info: title: Conduit Sandbox API description: >- **Sandbox API** — clients integrate against this surface to exercise happy and unhappy paths without consuming real KYC/PSP credits or moving real money. Customer KYC, banking partners, and crypto custody are stubbed; org-level KYB runs against real providers. Simulation endpoints under `/v2/sandbox/*` drive specific scenarios. Internal and portal endpoints are excluded from this spec. version: '2.0' contact: {} servers: - url: https://api.sandbox.conduit.financial/v2 description: Sandbox - url: https://api.conduit.financial/v2 description: Production security: - api-key: [] tags: - name: Customers - name: Registered Addresses - name: Wallets - name: Wallet Signers - name: Signing Quorum - name: Virtual Accounts - name: Applications - name: Documents - name: Verifications - name: Signing Requests - name: Transactions - name: Payouts - name: Whitelist Recipients - name: Orders - name: RFIs - name: Webhook Endpoints - name: Webhook Deliveries - name: Webhook Event Types - name: Features - name: Customer Onboarding - name: Sandbox paths: /webhooks/deliveries: get: tags: - Webhook Deliveries summary: List webhook deliveries description: >- Returns a paginated list of delivery attempts for the authenticated organization. Optionally filter by `endpointId`, by delivery `status` (`pending`, `processing`, `succeeded`, `failed`), or by `eventType` (exact match, e.g. `transaction.failed`). An unknown `status` value returns 400; an unknown `eventType` returns an empty page. operationId: WebhookDeliveriesController_listDeliveries_v2 parameters: - name: cursor required: false in: query description: Opaque cursor from a previous response to fetch the next page x-nestjs_zod-parent-additional-properties: false schema: type: string maxLength: 500 - name: limit required: false in: query description: Maximum number of results to return (1-100) x-nestjs_zod-parent-additional-properties: false schema: minimum: 1 maximum: 100 default: 20 type: number - name: direction required: false in: query description: Pagination direction relative to the cursor x-nestjs_zod-parent-additional-properties: false schema: enum: - forward - backward type: string - name: endpointId required: false in: query description: Only return deliveries targeted at this webhook endpoint x-nestjs_zod-parent-additional-properties: false schema: pattern: ^wep_[0-9A-Za-z]{22}$ type: string - name: status required: false in: query description: >- Filter by delivery status. Case-insensitive. An unknown value returns 400. x-nestjs_zod-parent-additional-properties: false schema: enum: - pending - processing - succeeded - failed type: string - name: eventType required: false in: query description: >- Filter by event type (exact match, e.g. `transaction.failed`). An unknown value returns an empty page. x-nestjs_zod-parent-additional-properties: false schema: minLength: 1 maxLength: 100 type: string responses: '200': description: '' content: application/json: schema: $ref: '#/components/schemas/PaginatedWebhookDeliveriesResponseDto' '400': description: >- **INVALID_OID_FORMAT**: A path or query parameter expected a valid object identifier but received a value that does not match the expected format. content: application/json: schema: $ref: '#/components/schemas/ValidationErrorDto' example: type: INVALID_OID_FORMAT title: Invalid Object ID Format status: 400 detail: >- A path or query parameter expected a valid object identifier but received a value that does not match the expected format. resolution: >- Verify that all IDs in the request URL and query parameters are correctly formatted. IDs are typically prefixed strings like 'cus_...', 'app_...', or 'doc_...'. docs: https://conduit-v2.mintlify.app/errors#invalid-oid-format instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' '401': description: >- **API_KEY_MISSING**: The request did not include an API key. All API requests must be authenticated. **API_KEY_INVALID**: The provided API key is not recognized or has been revoked. content: application/json: schema: $ref: '#/components/schemas/ProblemDetailDto' example: type: API_KEY_MISSING title: API Key Missing status: 401 detail: >- The request did not include an API key. All API requests must be authenticated. resolution: >- Include your API key in the 'x-api-key' header with every request. docs: https://conduit-v2.mintlify.app/errors#api-key-missing instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' '429': description: >- **RATE_LIMITED**: Too many requests. This error is returned by three independent checks: the per-organization bucket applied to every authenticated API request; the per-IP bucket applied to unauthenticated traffic before an API key is validated; and the per-IP bucket applied when repeated invalid API keys are submitted from the same address. Honor the Retry-After header (also exposed as retryAfterSeconds in the body) before retrying. Current limits and remaining budget are visible in X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset on rate-limited route responses. content: application/json: schema: $ref: '#/components/schemas/RateLimitedErrorDto' example: type: RATE_LIMITED title: Rate Limited status: 429 detail: >- Too many requests. This error is returned by three independent checks: the per-organization bucket applied to every authenticated API request; the per-IP bucket applied to unauthenticated traffic before an API key is validated; and the per-IP bucket applied when repeated invalid API keys are submitted from the same address. Honor the Retry-After header (also exposed as retryAfterSeconds in the body) before retrying. Current limits and remaining budget are visible in X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset on rate-limited route responses. resolution: >- Sleep until Retry-After seconds have elapsed, then retry. For sustained workloads exceeding the per-organization defaults, request a rate-limit increase through your support contact. docs: https://conduit-v2.mintlify.app/errors#rate-limited instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' retryAfterSeconds: 3 '500': description: >- **INTERNAL_ERROR**: An unexpected error occurred while processing your request. content: application/json: schema: $ref: '#/components/schemas/ProblemDetailDto' example: type: INTERNAL_ERROR title: Internal Error status: 500 detail: An unexpected error occurred while processing your request. resolution: >- Retry the request after a brief delay. If the error persists, contact support and include the correlationId from the error response for investigation. docs: https://conduit-v2.mintlify.app/errors#internal-error instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' components: schemas: PaginatedWebhookDeliveriesResponseDto: type: object properties: data: type: array items: type: object properties: id: type: string pattern: ^wdl_[0-9A-Za-z]{22}$ description: Unique webhook delivery identifier endpointId: type: string pattern: ^wep_[0-9A-Za-z]{22}$ description: The endpoint this delivery is targeted at eventType: type: string description: Event type that triggered this delivery example: customer.created payload: type: object properties: id: type: string description: Unique event identifier example: evt_2xKjF9mQb7vN4hL1pR3w8t type: type: string description: Event type that triggered this delivery example: customer.created createdAt: type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$ description: ISO 8601 timestamp when the event occurred example: '2026-01-15T09:30:00.000Z' apiVersion: type: string description: Public API major version. enum: - '2' mode: type: string enum: - live - sandbox description: >- Delivery mode of the event source. Lets a single endpoint receive both production and sandbox events without ambiguity. data: type: object additionalProperties: {} description: Event payload data, shape varies by event type. required: - id - type - createdAt - apiVersion - mode - data description: The webhook event payload status: description: Current delivery status type: string enum: - pending - processing - succeeded - failed attempts: type: number description: Number of delivery attempts made so far example: 1 maxAttempts: type: number description: Maximum number of delivery attempts before giving up example: 5 createdAt: type: string format: date-time description: ISO 8601 timestamp example: '2026-01-15T09:30:00.000Z' updatedAt: type: string format: date-time description: ISO 8601 timestamp example: '2026-01-15T09:30:00.000Z' completedAt: type: string format: date-time description: >- Timestamp when the delivery completed, null if still in progress example: '2026-01-15T09:30:00.000Z' nullable: true required: - id - endpointId - eventType - payload - status - attempts - maxAttempts - createdAt - updatedAt - completedAt meta: type: object properties: mode: type: string description: Pagination mode example: cursor enum: - cursor nextCursor: type: string description: Cursor for the next page, null if no more results example: eyJpZCI6ImN1c18yeFBxTjhSIn0 nullable: true previousCursor: type: string description: Cursor for the previous page, null if at the start example: null nullable: true total: type: number description: Total number of records matching the query example: 42 required: - mode - nextCursor - previousCursor - total required: - data - meta ValidationErrorDto: type: object properties: type: type: string description: Machine-readable error code example: CUSTOMER_NOT_FOUND title: type: string description: Human-readable error type label example: Customer Not Found status: type: number description: HTTP status code example: 404 detail: type: string description: Human-readable explanation of this occurrence example: Customer with id cus_abc123 not found resolution: type: string description: What the developer should do to resolve this error example: >- Verify the customer ID. Check you are using the correct API key for this organization. docs: type: string description: URL to error documentation example: https://conduit-v2.mintlify.app/errors#customer-not-found instance: type: string description: Request path that produced the error example: /v2/customers/cus_abc123 correlationId: description: Request correlation ID example: req_a1b2c3d4 type: string timestamp: type: string description: ISO 8601 UTC timestamp example: '2026-04-27T20:00:00.000Z' details: description: >- Additional structured data for domain-specific errors (e.g. missing field lists, pair info) errors: type: array items: type: object properties: pointer: type: string description: JSON pointer to the invalid field example: /email detail: type: string description: What is wrong with this field example: Invalid email format allowedValues: description: The values this field accepts, when it is a closed set example: - ach - fedwire - rtp type: array items: type: string category: description: >- Class of blocker (requirements-validator output only). 'field' = form-field gap, 'document' = missing or insufficient document (including per-UBO document slots), 'individual' = required person missing. example: field type: string enum: - field - document - individual required: - pointer - detail required: - type - title - status - detail - resolution - docs - instance - timestamp ProblemDetailDto: type: object properties: type: type: string description: Machine-readable error code example: CUSTOMER_NOT_FOUND title: type: string description: Human-readable error type label example: Customer Not Found status: type: number description: HTTP status code example: 404 detail: type: string description: Human-readable explanation of this occurrence example: Customer with id cus_abc123 not found resolution: type: string description: What the developer should do to resolve this error example: >- Verify the customer ID. Check you are using the correct API key for this organization. docs: type: string description: URL to error documentation example: https://conduit-v2.mintlify.app/errors#customer-not-found instance: type: string description: Request path that produced the error example: /v2/customers/cus_abc123 correlationId: description: Request correlation ID example: req_a1b2c3d4 type: string timestamp: type: string description: ISO 8601 UTC timestamp example: '2026-04-27T20:00:00.000Z' details: description: >- Additional structured data for domain-specific errors (e.g. missing field lists, pair info) required: - type - title - status - detail - resolution - docs - instance - timestamp RateLimitedErrorDto: type: object properties: type: type: string description: Machine-readable error code example: CUSTOMER_NOT_FOUND title: type: string description: Human-readable error type label example: Customer Not Found status: type: number description: HTTP status code example: 404 detail: type: string description: Human-readable explanation of this occurrence example: Customer with id cus_abc123 not found resolution: type: string description: What the developer should do to resolve this error example: >- Verify the customer ID. Check you are using the correct API key for this organization. docs: type: string description: URL to error documentation example: https://conduit-v2.mintlify.app/errors#customer-not-found instance: type: string description: Request path that produced the error example: /v2/customers/cus_abc123 correlationId: description: Request correlation ID example: req_a1b2c3d4 type: string timestamp: type: string description: ISO 8601 UTC timestamp example: '2026-04-27T20:00:00.000Z' details: description: >- Additional structured data for domain-specific errors (e.g. missing field lists, pair info) retryAfterSeconds: type: integer minimum: 0 exclusiveMinimum: true maximum: 9007199254740991 description: Seconds to wait before retrying example: 3 required: - type - title - status - detail - resolution - docs - instance - timestamp - retryAfterSeconds securitySchemes: api-key: type: apiKey in: header name: x-api-key ````