> ## 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 operations > Returns a paginated list of money transfer operations for the authenticated partner. Filter by referenceId, userId, linkId, status, and date range. Each operation includes the full amount breakdown (send, receive, rate, fee). ## OpenAPI ````yaml /raas-widgets/openapi.json get /partner/operations 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/operations: get: tags: - Partner - Operations summary: List operations description: >- Returns a paginated list of money transfer operations for the authenticated partner. Filter by referenceId, userId, linkId, status, and date range. Each operation includes the full amount breakdown (send, receive, rate, fee). operationId: OperationsController_listOperations parameters: - name: referenceId required: false in: query description: Filter operations by the partner reference ID of the associated user schema: example: user-12345 type: string - name: userId required: false in: query description: Filter operations by M2M user ID schema: example: user_acme_x1y2z3 type: string - name: linkId required: false in: query description: Filter operations by the magic link ID that initiated the transfer schema: example: link_acme_a1b2c3d4e5f6 type: string - name: externalId required: false in: query description: >- Filter by the partner-supplied external tracing ID set when the magic link was created schema: example: ORD-2026-001 type: string - name: status required: false in: query description: >- Filter by operation status. "created" = operation initiated. "processing" = funds in transit. "completed" = transfer successful. "failed" = transfer failed. "cancelled" = operation cancelled. schema: example: completed enum: - created - processing - completed - failed - cancelled type: string - name: fundingMethod required: false in: query description: >- Filter by the canonical funding method used to fund the operation (e.g. DEBIT_CARD, ACH, CASH_DEPOSIT). Matches `funding.method`. schema: example: CASH_DEPOSIT type: string - name: pendingFunding required: false in: query description: >- When true, returns only operations that are still pending funding: their funding status is not `funded`/`expired` and the operation is not in a terminal status (completed/failed/cancelled). Useful to attach a cash-deposit payment to an operation awaiting funds. schema: type: boolean example: true - name: from required: false in: query description: Filter operations 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 operations created on or before this date (ISO 8601) schema: example: '2026-02-28T23:59:59.999Z' type: string - 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 responses: '200': description: Paginated list of operations content: application/json: schema: $ref: '#/components/schemas/ListOperationsResponseDto' '401': description: Unauthorized — invalid or missing API key / bearer token security: - api-key: [] components: schemas: ListOperationsResponseDto: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/ListOperationsDataDto' required: - success - data ListOperationsDataDto: type: object properties: items: description: Array of operations type: array items: $ref: '#/components/schemas/OperationListItemDto' pagination: $ref: '#/components/schemas/PaginationMetaDto' required: - items - pagination OperationListItemDto: type: object properties: operationId: type: string description: Unique operation identifier example: op_acme_abc123 userId: type: string description: M2M user ID example: user_acme_x1y2z3 referenceId: type: string description: Partner reference ID for the user example: user-12345 linkId: type: string description: Link ID that initiated this operation example: link_acme_a1b2c3d4e5f6 status: type: string description: Operation status example: completed enum: - created - processing - completed - failed - cancelled flowState: type: string description: >- Canonical FSM state (operation-lifecycle.fsm.ts). More granular than `status` — reflects the current lifecycle step. example: provisioning enum: - identity_pending - identity_review - limits_check - limits_review - provisioning - funding - awaiting_funding - executing - executed - completed - failed - cancelled - provisioning_error - execution_error - limits_blocked funding: type: object description: Funding method details fundingStatus: type: string description: Push-funding sub-status (cash deposit corridors) example: awaiting_funding payout: type: object description: Payout method details amount: description: Transfer amount breakdown allOf: - $ref: '#/components/schemas/OperationAmountDto' createdAt: type: string description: Operation creation timestamp (ISO 8601) example: '2026-02-10T12:00:00.000Z' completedAt: type: string description: When the operation completed (ISO 8601) example: '2026-02-10T12:05:00.000Z' failedAt: type: string description: When the operation failed (ISO 8601) failureReason: type: string description: Reason for failure if the operation failed example: Insufficient funds externalId: type: string description: Partner tracing ID copied from the magic link example: ORD-2026-001 required: - operationId - userId - linkId - status - amount - createdAt PaginationMetaDto: type: object properties: page: type: number description: Current page number example: 1 limit: type: number description: Number of items per page example: 20 total: type: number description: Total number of items matching the query example: 85 totalPages: type: number description: Total number of pages example: 5 required: - page - limit - total - totalPages OperationAmountDto: type: object properties: send: type: number description: Amount sent by the user in source currency example: 100 receive: type: number description: Amount the recipient receives in destination currency example: 1725 rate: type: number description: Exchange rate applied example: 17.25 fee: type: number description: Fee charged for the transfer example: 3.99 currency: type: object description: Currency information example: source: USD destination: MXN required: - send - receive - rate - fee - currency 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. ````