> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leapfinancial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List webhook deliveries

> Returns a paginated list of webhook delivery attempts for the authenticated partner. Filter by event type, delivery status, linkId, referenceId, userId, and date range.



## OpenAPI

````yaml /raas-widgets/openapi.json get /partner/webhooks/deliveries
openapi: 3.0.0
info:
  title: RaaS Widgets Partner API
  description: >
    REST API for RaaS Widgets partner integrations. Create magic links for
    embeddable flows, manage end users, track transfer operations, handle CIP
    verification, and configure webhooks for real-time event notifications.


    This specification covers the **Partner-accessible API** only (`X-API-Key`
    against `/partner/*`). Widget and Superadmin APIs are out of scope.


    ## Authentication


    All endpoints require an API key passed in the `X-API-Key` header. Use
    `raas_sandbox_*` keys for the sandbox environment and `raas_live_*` keys for
    production.


    ## Environments


    | Environment | Base URL |

    |---|---|

    | Sandbox | `https://raas-widgets-backend-sandbox.up.railway.app` |
  version: 1.18.0
  contact: {}
servers:
  - url: https://raas-widgets-backend-sandbox.up.railway.app
    description: Sandbox
security: []
tags:
  - name: Partner - Magic Links
    description: Create, list, and manage magic links for flows
  - name: Partner - Flows
    description: List enabled flows and the full flow catalog
  - name: Partner - Users
    description: View and manage end users associated with your partner account
  - name: Partner - Operations
    description: Track money transfer operations and their statuses
  - name: Partner - Requests
    description: List and inspect money-request records
  - name: Partner - Deferred Payouts
    description: List, inspect, and cancel deferred payout remittances
  - name: Partner - CIP
    description: Customer Identification Program (CIP) verification management
  - name: Partner - Data Requests
    description: Fulfill data requests for additional user information
  - name: Partner - Settings
    description: Configure partner-level settings (redirect URLs, logo, etc.)
  - name: Partner - Webhooks
    description: Configure webhook endpoints and inspect delivery history
  - name: Partner - Pricing
    description: >-
      Indicative pre-quote summaries (best / worst / averages) for partner
      integrations
paths:
  /partner/webhooks/deliveries:
    get:
      tags:
        - Partner - Webhooks
      summary: List webhook deliveries
      description: >-
        Returns a paginated list of webhook delivery attempts for the
        authenticated partner. Filter by event type, delivery status, linkId,
        referenceId, userId, and date range.
      operationId: PartnerWebhooksController_listDeliveries
      parameters:
        - name: page
          required: false
          in: query
          description: Page number (1-indexed)
          schema:
            minimum: 1
            default: 1
            example: 1
            type: number
        - name: limit
          required: false
          in: query
          description: Number of items per page
          schema:
            minimum: 1
            maximum: 100
            default: 20
            example: 20
            type: number
        - name: from
          required: false
          in: query
          description: Filter records created on or after this date (ISO 8601)
          schema:
            example: '2026-01-01T00:00:00.000Z'
            type: string
        - name: to
          required: false
          in: query
          description: Filter records created on or before this date (ISO 8601)
          schema:
            example: '2026-02-28T23:59:59.999Z'
            type: string
        - name: event
          required: false
          in: query
          description: >-
            Filter by event type (e.g., link.opened, operation.completed,
            user.data_request)
          schema:
            example: operation.completed
            type: string
        - name: status
          required: false
          in: query
          description: >-
            Filter by delivery status. "pending" = not yet attempted.
            "delivered" = webhook received 2xx response. "failed" = delivery
            failed after retries.
          schema:
            example: delivered
            enum:
              - pending
              - delivered
              - failed
            type: string
        - name: linkId
          required: false
          in: query
          description: Filter deliveries related to a specific magic link
          schema:
            example: link_acme_a1b2c3d4e5f6
            type: string
        - name: referenceId
          required: false
          in: query
          description: Filter deliveries by the partner reference ID of the associated user
          schema:
            example: user-12345
            type: string
        - name: userId
          required: false
          in: query
          description: Filter deliveries by M2M user ID
          schema:
            example: user_acme_x1y2z3
            type: string
      responses:
        '200':
          description: Paginated list of webhook deliveries
        '401':
          description: Unauthorized — invalid or missing API key / bearer token
      security:
        - api-key: []
components:
  securitySchemes:
    api-key:
      type: apiKey
      in: header
      name: X-API-Key
      description: >-
        Your partner API key. Use `raas_sandbox_*` keys for the sandbox
        environment and `raas_live_*` keys for production.

````