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

# Get a wallet-provisioning operation

> Fetch a wallet-provisioning operation — the status resource a `202` from POST /wallets points at. Project-scoped to the caller.



## OpenAPI

````yaml /api-reference/openapi.yaml get /wallets/operations/{operationId}
openapi: 3.0.3
info:
  title: Polygon OMS Public API
  version: v26.09.09-0001
  description: >-
    Unified API for moving money between crypto and fiat. Three ways to move
    money: Transactions (instant, wallet or card funded, including Cash-In for
    in-person cash deposits), Deposit Addresses (reusable crypto deposit
    configurations), and Virtual Accounts (dedicated bank accounts that
    auto-convert fiat to crypto). Standard transactions follow a two-step flow:
    create a Quote (pricing), then create a Transaction (execution). Cash-in
    codes generate a one-time deposit code for in-person cash deposits at retail
    locations.
  contact:
    name: Polygon OMS
    url: https://oms.polygon.technology
servers:
  - url: https://sandbox-api.polygon.technology/v0.13
    description: Sandbox
  - url: https://api.polygon.technology/v0.13
    description: Production
security:
  - BearerAuth: []
tags:
  - name: Auth
    description: Authentication via FrontEgg
  - name: Customers
    description: Customer management and KYC
  - name: Customer
  - name: Wallet
  - name: Quote
  - name: Transaction
  - name: CashIns
  - name: CashLocation
  - name: Sandbox
  - name: VirtualAccount
  - name: Counterparty
  - name: ExternalAccount
  - name: Reference
  - name: DepositAddress
paths:
  /wallets/operations/{operationId}:
    get:
      tags:
        - Wallet
      summary: Get a wallet-provisioning operation
      description: >-
        Fetch a wallet-provisioning operation — the status resource a `202` from
        POST /wallets points at. Project-scoped to the caller.
      operationId: getWalletOperation
      parameters:
        - name: operationId
          in: path
          required: true
          description: Operation ID (`op_` prefix).
          schema:
            type: string
      responses:
        '200':
          description: The request has succeeded.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WalletOperation'
components:
  schemas:
    WalletOperation:
      type: object
      required:
        - operationId
        - object
        - customerId
        - status
        - pairs
        - createdAt
      properties:
        operationId:
          allOf:
            - $ref: '#/components/schemas/typeId'
          description: Operation ID (`op_` TypeID).
        object:
          type: string
          enum:
            - wallet.operation
          description: Resource type discriminator. Always "wallet.operation".
        customerId:
          allOf:
            - $ref: '#/components/schemas/typeId'
          description: >-
            The OMS customer the operation provisions wallets for (`cst_`
            prefix).
        status:
          $ref: '#/components/schemas/WalletOperationStatus'
        pairs:
          type: array
          items:
            $ref: '#/components/schemas/WalletOperationPairStatus'
        walletId:
          allOf:
            - $ref: '#/components/schemas/typeId'
          description: >-
            The provisioned wallet's id (`wlt_` prefix), present once the
            requested pair has completed and the wallet record is visible.
        createdAt:
          type: string
          format: date-time
      description: >-
        The status resource a `202 Accepted` wallet create points at (its
        `Location` header). Project-scoped: an operation is only visible to the
        project that created it. Poll until `status` leaves `pending`; when the
        requested wallet is confirmed, `walletId` carries its id.
    typeId:
      type: string
      pattern: >-
        ^[a-z]+_([0-9a-hjkmnp-tv-z]{26}|[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})$
      description: >-
        Public TypeID, e.g. `txn_01h455vb4pex5vsknk084sn02q`; legacy UUID
        suffixes are accepted until non-v7 rows are retired.
      x-go-type: string
    WalletOperationStatus:
      type: string
      enum:
        - pending
        - complete
        - partial
        - terminal
      description: >-
        Aggregate status of a wallet-provisioning operation. `pending`: at least
        one pair is still converging and automation is active. `partial`: some
        pairs completed, at least one needs an operator. `terminal`: the
        provider durably rejected at least one pair. `complete`: every pair
        confirmed.
    WalletOperationPairStatus:
      type: object
      required:
        - asset
        - network
        - state
      properties:
        asset:
          type: string
          description: Crypto asset (canonical symbol, e.g. "usdc").
        network:
          type: string
          description: Blockchain network (canonical name, e.g. "polygon").
        state:
          $ref: '#/components/schemas/WalletOperationPairState'
      description: >-
        One asset/network pair being converged by a wallet-provisioning
        operation.
    WalletOperationPairState:
      type: string
      enum:
        - pending
        - complete
        - terminal
      description: >-
        Per-pair convergence state on a wallet-provisioning operation.
        `terminal` means the provider durably rejected the pair.
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Token from POST /auth/token

````