> ## 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 status

> Retrieves a recent partial snapshot of processing or delivery status for a transaction.

The initial status is `Sent`. While the operation is still in progress, before it settles as `Completed` or `Failed`, the status may move through intermediate values that belong to the enumeration below (for example `Funding`, `Funded`, `OnHold`, or `InTransit`).

Possible statuses: `Sent`, `Funding`, `Funded`, `Completed`, `Failed`, `OnHold`, `InTransit`, `Cancelled`.



## OpenAPI

````yaml /raas/swagger-partner.json get /user/operations/status/{userToken}/{operationId}
openapi: 3.0.0
info:
  title: ''
  version: 0.0.1
servers:
  - url: https://raas-partner-cv.nomas.cash/v1
security: []
paths:
  /user/operations/status/{userToken}/{operationId}:
    get:
      tags:
        - Operations
      summary: Get operation status
      description: >-
        Retrieves a recent partial snapshot of processing or delivery status for
        a transaction.


        The initial status is `Sent`. While the operation is still in progress,
        before it settles as `Completed` or `Failed`, the status may move
        through intermediate values that belong to the enumeration below (for
        example `Funding`, `Funded`, `OnHold`, or `InTransit`).


        Possible statuses: `Sent`, `Funding`, `Funded`, `Completed`, `Failed`,
        `OnHold`, `InTransit`, `Cancelled`.
      operationId: getOperationStatus
      parameters:
        - description: User involved in the transaction.
          in: path
          name: userToken
          required: true
          schema:
            type: string
        - description: Correlation ID.
          in: path
          name: operationId
          required: true
          schema:
            type: string
      responses:
        '200':
          description: >-
            **200 — OK.** Status string for the operation.


            The initial status is `Sent`. While the operation is still in
            progress, before it settles as `Completed` or `Failed`, the status
            may move through intermediate values that belong to the enumeration
            below (for example `Funding`, `Funded`, `OnHold`, or `InTransit`).


            Possible statuses: `Sent`, `Funding`, `Funded`, `Completed`,
            `Failed`, `OnHold`, `InTransit`, `Cancelled`.


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Status read | Resolved `userToken` + valid `operationId`. | Plain
            string, one of the statuses above |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-operation-status-scenario-matrix).
          content:
            application/json:
              schema:
                type: string
              example: Completed
        '400':
          description: >-
            **400 — Bad request.**


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Service rejected | `NumiBadRequestError` from operation service. |
            `ErrorResponse` with mapped `code` |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-operation-status-scenario-matrix).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                reason: Bad request from operation service.
        '401':
          description: >-
            **401 — Unauthorized.**


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Missing / bad API key | Omit `api_key` or invalid `partner` /
            `partner_send` key. | OpenAPI `401` via `@Response<ErrorResponse>`.
            |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-operation-status-scenario-matrix).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                reason: Missing or invalid API key
        '404':
          description: >-
            **404 — Not found.** User from path not found.


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Unknown path user | `userToken` does not resolve. |
            `ERROR_USER_NOT_FOUND` |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-operation-status-scenario-matrix).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                reason: User not found for path userToken.
        '500':
          description: >-
            **500 — Internal server error.**


            **Scenarios for this response**:


            | Scenario | How to reproduce | Typical `code` / body |

            |------------|------------------|------------------------|

            | Unexpected | Non-Numi errors or `NumiError` after bad-request
            branch. | `ERROR_INTERNAL_SERVER_ERROR` or `NumiError` `errorCode` |


            See also [Full scenario
            matrix](/raas/guides/testing-sandbox#get-operation-status-scenario-matrix).
          content:
            application/json:
              schema:
                properties:
                  reason:
                    type: string
                required:
                  - reason
                type: object
              example:
                reason: An unhandled error has occurred
      security:
        - api_key:
            - partner
            - partner_send
components:
  schemas:
    ErrorResponse:
      properties:
        detail:
          type: string
        code:
          type: string
        reason:
          type: string
      required:
        - code
        - reason
      type: object
  securitySchemes:
    api_key:
      type: apiKey
      name: api_key
      in: header

````