> ## 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. # Get operation details > Returns full details of a specific money transfer operation including amount breakdown, funding and payout method details, status timeline, and failure reason if applicable. ## OpenAPI ````yaml /raas-widgets/openapi.json get /partner/operations/{operationId} 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/{operationId}: get: tags: - Partner - Operations summary: Get operation details description: >- Returns full details of a specific money transfer operation including amount breakdown, funding and payout method details, status timeline, and failure reason if applicable. operationId: OperationsController_getOperation parameters: - name: operationId required: true in: path description: Unique operation identifier schema: example: op_acme_abc123 type: string responses: '200': description: Operation details retrieved content: application/json: schema: $ref: '#/components/schemas/OperationDetailResponseDto' '401': description: Unauthorized — invalid or missing API key / bearer token '404': description: Operation not found security: - api-key: [] components: schemas: OperationDetailResponseDto: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/OperationDetailDataDto' required: - success - data OperationDetailDataDto: 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 raasOperationId: type: string description: External RaaS operation ID for cross-referencing example: raas_op_xyz789 status: type: string description: Operation status example: completed enum: - created - processing - completed - failed - cancelled funding: type: object description: Funding method details payout: type: object description: Payout method details amount: description: Transfer amount breakdown allOf: - $ref: '#/components/schemas/OperationAmountDto' flowState: type: string description: Current FSM state of the operation lifecycle example: executed enum: - identity_pending - identity_review - provisioning - provisioning_error - executing - executed - execution_error - completed - failed - cancelled corridor: type: string description: Corridor that owns/executes this operation example: CRB_INTERMEX fundingStatus: type: string description: Push-funding sub-status (cash deposit corridors) example: awaiting_funding executionRefs: description: Provider-agnostic execution references allOf: - $ref: '#/components/schemas/ExecutionRefsDto' stateHistory: description: Ordered history of FSM state transitions type: array items: $ref: '#/components/schemas/StateHistoryEntryDto' raasCommit: description: Execution request/response/error against the corridor provider allOf: - $ref: '#/components/schemas/RaasCommitDto' cancellationReason: type: string description: Reason for cancellation if the operation was cancelled createdAt: type: string description: Operation creation timestamp (ISO 8601) example: '2026-02-10T12:00:00.000Z' updatedAt: type: string description: Last update timestamp (ISO 8601) example: '2026-02-10T12:05: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 externalId: type: string description: Partner tracing ID copied from the magic link example: ORD-2026-001 required: - operationId - userId - linkId - status - amount - stateHistory - createdAt - updatedAt 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 ExecutionRefsDto: type: object properties: corridor: type: string description: Corridor that executed the operation example: CRB_INTERMEX nativeOperationId: type: string description: Native operation id at the corridor provider status: type: string description: Native execution status required: - corridor StateHistoryEntryDto: type: object properties: state: type: string description: FSM state name example: executing timestamp: type: string description: When the FSM entered this state (ISO 8601) example: '2026-02-10T12:01:00.000Z' metadata: description: Diagnostic metadata captured for this transition allOf: - $ref: '#/components/schemas/StateHistoryMetadataDto' required: - state - timestamp RaasCommitDto: type: object properties: request: type: object description: Request payload sent to the corridor provider response: type: object description: Response payload returned by the corridor provider error: description: Error captured when the execution failed allOf: - $ref: '#/components/schemas/RaasCommitErrorDto' committedAt: type: string description: When the execution was attempted (ISO 8601) success: type: boolean description: Whether the execution succeeded example: false required: - request - success StateHistoryMetadataDto: type: object properties: event: type: string description: Canonical FSM event that triggered the transition example: EXECUTION_REJECTED phase: type: string description: Operational phase of the transition example: execution corridor: type: string description: Corridor that owns the transition example: CRB_INTERMEX error: type: string description: Error message captured when the FSM entered an error state example: '[PAYMENT_METHOD_INVALID] ...' httpStatus: type: number description: HTTP status of the underlying failure, when applicable example: 422 RaasCommitErrorDto: type: object properties: message: type: string description: Error message returned by the corridor provider httpStatus: type: number description: HTTP status returned by the corridor provider example: 422 code: type: string description: Provider error code example: PAYHUB_ERROR details: type: object description: Raw provider details payload, when present validations: description: Validation messages split into a legible list example: - sender.phoneNumber should not be empty - recipient.city should not be empty type: array items: type: string required: - message 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. ````