> ## Documentation Index > Fetch the complete documentation index at: https://ramps-kph-document-3ds-password.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Get a stablecoin issuer operation > Retrieve a single stablecoin issuer operation by its Grid identifier. ## OpenAPI ````yaml https://app.stainless.com/api/spec/documented/grid/openapi.documented.yml get /stablecoin-operations/{stablecoinOperationId} openapi: 3.1.0 info: title: Grid API description: > API for managing global payments on the open Money Grid. Built by Lightspark. See the full documentation at https://docs.lightspark.com/. version: '2025-10-13' contact: name: Lightspark Support email: support@lightspark.com license: name: Proprietary url: https://lightspark.com/terms servers: - url: https://api.lightspark.com/grid/2025-10-13 description: Production server security: - BasicAuth: [] - AgentAuth: [] tags: - name: Platform Configuration description: >- Platform configuration endpoints for managing global settings. You can also configure these settings in the Grid dashboard. - name: Customers description: >- Customer management endpoints for creating and updating customer information - name: Contact Verification description: >- Endpoints for verifying a customer's email and phone via one-time codes. Required only for customers whose payment provider mandates contact verification (e.g. EU customers); other providers return 409. - name: Strong Customer Authentication description: >- Endpoints for authorizing money-movement operations that require Strong Customer Authentication. Relevant only for customers in a region where SCA is required (e.g. EU); customers outside SCA-regulated regions never see an SCA challenge and these endpoints return 409. - name: KYC/KYB Verifications description: >- Endpoints for Know Your Customer (KYC) and Know Your Business (KYB) verification, including managing beneficial owners and triggering verification for customers. - name: Documents description: >- Endpoints for uploading and managing verification documents for customers and beneficial owners. Supports KYC and KYB document requirements. - name: Internal Accounts description: >- Internal account management endpoints for creating and managing internal accounts - name: External Accounts description: >- External account management endpoints for creating and managing external bank accounts - name: Same-Currency Transfers description: >- Endpoints for transferring funds between internal and external accounts with the same currency - name: Cross-Currency Transfers description: Endpoints for creating and confirming quotes for cross-currency transfers - name: Transactions description: Endpoints for retrieving transaction information - name: Webhooks description: Webhook endpoints and configuration for receiving notifications - name: Invitations description: Endpoints for creating, claiming and managing UMA invitations - name: Sandbox description: Endpoints to trigger test cases in sandbox - name: API Tokens description: Endpoints to programmatically manage API tokens - name: Exchange Rates description: >- Endpoints for retrieving cached foreign exchange rates. Rates are cached for approximately 5 minutes and include platform-specific fees. - name: Discoveries description: >- Endpoints for discovering available payment rails, banks, and providers for a given country and currency corridor. - name: Embedded Wallet Auth description: >- Endpoints for registering and verifying end-user authentication credentials (email OTP, OAuth, passkey) used to sign Embedded Wallet actions. - name: Agent Management description: >- Endpoints for creating and managing agents (experimental), called by the partner's backend using platform credentials. Covers the full agent lifecycle: creation, policy configuration, pausing, deletion, the device code installation flow, and approving or rejecting transactions initiated by agents. - name: Agent Operations description: >- Endpoints called by the agent itself using its own credentials (obtained via device code redemption). Scoped to the agent's associated customer — all requests automatically operate on behalf of that customer and are subject to the agent's policy. When an action requires approval, the resulting transaction enters a pending state and must be approved by the platform via `POST /transactions/{transactionId}/approve`. - name: Cards description: >- Card management endpoints. Issue debit cards against an internal account, freeze / unfreeze, close, manage card funding sources, and list card transactions. - name: Stablecoins description: >- Stablecoin issuance endpoints. Link provider accounts, register provider-created stablecoins, create direct mint/burn issuer operations, and track operation status. paths: /stablecoin-operations/{stablecoinOperationId}: parameters: - name: stablecoinOperationId in: path description: System-generated stablecoin issuer operation identifier required: true schema: type: string get: tags: - Stablecoins summary: Get a stablecoin issuer operation description: Retrieve a single stablecoin issuer operation by its Grid identifier. operationId: getStablecoinOperation responses: '200': description: Successful operation content: application/json: schema: $ref: '#/components/schemas/StablecoinOperation' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Error401' '404': description: Stablecoin operation not found content: application/json: schema: $ref: '#/components/schemas/Error404' '500': description: Internal service error content: application/json: schema: $ref: '#/components/schemas/Error500' security: - BasicAuth: [] components: schemas: StablecoinOperation: type: object required: - id - stablecoinId - operationType - status - amount - provider - providerEnvironment - stablecoinProviderAccountId - createdAt - updatedAt properties: id: type: string description: System-generated stablecoin issuer operation identifier. example: StablecoinOperation:019542f5-b3e7-1d02-0000-000000000301 stablecoinId: type: string description: Stablecoin this operation belongs to. example: Stablecoin:019542f5-b3e7-1d02-0000-000000000002 operationType: $ref: '#/components/schemas/StablecoinOperationType' status: $ref: '#/components/schemas/StablecoinOperationStatus' amount: type: string description: Operation amount in the stablecoin's smallest unit. example: '1000000' provider: $ref: '#/components/schemas/StablecoinProvider' providerEnvironment: $ref: '#/components/schemas/StablecoinProviderEnvironment' stablecoinProviderAccountId: type: string description: Stablecoin provider account link used for the operation. example: StablecoinProviderAccount:019542f5-b3e7-1d02-0000-000000000001 source: $ref: '#/components/schemas/StablecoinOperationSource' fundingInstructions: $ref: '#/components/schemas/StablecoinFundingInstructions' destination: $ref: '#/components/schemas/StablecoinOperationDestination' estimatedDelivery: $ref: '#/components/schemas/StablecoinEstimatedDelivery' expiresAt: type: string format: date-time description: Expiry for operations awaiting external funding. example: '2026-05-27T16:40:00Z' providerStatus: type: string description: Sanitized provider status when available. example: pending failureReason: type: string description: Stable internal failure code for terminal failed operations. example: PROVIDER_TRANSFER_FAILED description: type: string description: Platform-provided operation description. example: Initial program funding mint createdAt: type: string format: date-time description: Creation timestamp. example: '2026-05-20T16:40:00Z' updatedAt: type: string format: date-time description: Last update timestamp. example: '2026-05-20T17:10:00Z' Error401: type: object required: - message - status - code properties: status: type: integer enum: - 401 description: HTTP status code code: type: string description: > | Error Code | Description | |------------|-------------| | UNAUTHORIZED | Issue with API credentials | | INVALID_SIGNATURE | Signature header is invalid | | WALLET_SIGNATURE_MISSING | The `Grid-Wallet-Signature` header is required for this Embedded Wallet action but was not supplied | | WALLET_SIGNATURE_MALFORMED | The `Grid-Wallet-Signature` header could not be parsed (bad encoding, structure, or fields) | | WALLET_SIGNATURE_BODY_MISMATCH | The `Grid-Wallet-Signature` was computed over a different request body than the one received | | WALLET_SIGNATURE_INVALID | The `Grid-Wallet-Signature` failed cryptographic verification against the registered credential | | REQUEST_ID_MISSING | The `Request-Id` header is required on the signed retry but was not supplied (paired with `Grid-Wallet-Signature`) | enum: - UNAUTHORIZED - INVALID_SIGNATURE - WALLET_SIGNATURE_MISSING - WALLET_SIGNATURE_MALFORMED - WALLET_SIGNATURE_BODY_MISMATCH - WALLET_SIGNATURE_INVALID - REQUEST_ID_MISSING message: type: string description: Error message details: type: object description: Additional error details additionalProperties: true Error404: type: object required: - message - status - code properties: status: type: integer enum: - 404 description: HTTP status code code: type: string description: > | Error Code | Description | |------------|-------------| | TRANSACTION_NOT_FOUND | Transaction not found | | INVITATION_NOT_FOUND | Invitation not found | | USER_NOT_FOUND | Customer not found | | QUOTE_NOT_FOUND | Quote not found | | LOOKUP_REQUEST_NOT_FOUND | Lookup request not found | | TOKEN_NOT_FOUND | Token not found | | BULK_UPLOAD_JOB_NOT_FOUND | Bulk upload job not found | | REFERENCE_NOT_FOUND | Reference not found | | UMA_NOT_FOUND | The UMA address is well-formed but no receiver exists at the counterparty VASP | | STABLECOIN_PROVIDER_ACCOUNT_NOT_FOUND | Stablecoin provider account link not found | enum: - TRANSACTION_NOT_FOUND - INVITATION_NOT_FOUND - USER_NOT_FOUND - QUOTE_NOT_FOUND - LOOKUP_REQUEST_NOT_FOUND - TOKEN_NOT_FOUND - BULK_UPLOAD_JOB_NOT_FOUND - REFERENCE_NOT_FOUND - UMA_NOT_FOUND - STABLECOIN_PROVIDER_ACCOUNT_NOT_FOUND message: type: string description: Error message details: type: object description: Additional error details additionalProperties: true Error500: type: object required: - message - status - code properties: status: type: integer enum: - 500 description: HTTP status code code: type: string description: | | Error Code | Description | |------------|-------------| | GRID_SWITCH_ERROR | Grid switch error | | INTERNAL_ERROR | Internal server or UMA error | enum: - GRID_SWITCH_ERROR - INTERNAL_ERROR message: type: string description: Error message details: type: object description: Additional error details additionalProperties: true StablecoinOperationType: type: string enum: - MINT - BURN description: Stablecoin issuer operation type. StablecoinOperationStatus: type: string enum: - CREATED - PENDING_FUNDING - PENDING_PROVIDER - PROCESSING - COMPLETED - FAILED - EXPIRED description: Stablecoin issuer operation lifecycle status. StablecoinProvider: type: string enum: - BRALE description: >- Stablecoin provider backing the linked account, stablecoin, or operation. StablecoinProviderEnvironment: type: string enum: - SANDBOX - PRODUCTION description: Provider environment derived from the authenticated Grid platform mode. StablecoinOperationSource: type: object description: >- Source of a stablecoin operation, as reported on a `StablecoinOperation`. A single merged shape (superset of the mint funding source and burn source request variants) so the field is unambiguously deserializable regardless of operation type: `externalAccountId` is present for external-account funded mints and external-account burns, `accountId` for Grid internal account sources, and `sourceTokenIdentifier`/`cryptoNetwork` for provider internal balance sources. required: - type properties: type: type: string enum: - WIRE - ACH_DEBIT - SAME_DAY_ACH_DEBIT - EXTERNAL_ACCOUNT - GRID_INTERNAL_ACCOUNT - PROVIDER_INTERNAL_BALANCE description: >- Source variant. Mint funding uses `WIRE`, `ACH_DEBIT`, or `SAME_DAY_ACH_DEBIT`; burns use `EXTERNAL_ACCOUNT`. `GRID_INTERNAL_ACCOUNT` and `PROVIDER_INTERNAL_BALANCE` are shared across mint and burn. example: ACH_DEBIT externalAccountId: type: string description: >- Grid `ExternalAccount` funding the operation, present for ACH debit mints and external-account burns. example: ExternalAccount:019542f5-b3e7-1d02-0000-000000000101 accountId: type: string description: Grid internal account id, present for Grid internal account sources. example: InternalAccount:019542f5-b3e7-1d02-0000-000000000102 sourceTokenIdentifier: type: string description: >- Provider token/value type, present for provider internal balance sources. example: USDC cryptoNetwork: type: string description: >- Source crypto network, present for provider internal balance sources. example: SOLANA StablecoinFundingInstructions: type: object description: >- Provider funding instructions safe to show publicly. Present for wire-funded mint operations and external-source burn operations when available. The common fields below are always declared; the exact set of remaining fields is rail- and provider-specific (for example, wire instructions carry bank beneficiary/account/routing details while Spark and on-chain instructions carry a deposit address), so `additionalProperties` stays open to pass those through without a spec change per rail. additionalProperties: true properties: rail: type: string description: Funding rail these instructions apply to (e.g. `SPARK`, `WIRE`). example: SPARK network: type: string description: Network the funds should be sent on, when applicable. example: SPARK address: type: string description: >- Deposit address the issuer sends funds to, for on-chain or Spark rails. example: spark1... valueType: type: string description: Provider token/value type the deposit address expects. example: ACME example: rail: SPARK network: SPARK address: spark1... valueType: ACME StablecoinOperationDestination: type: object description: >- Destination of a stablecoin operation, as reported on a `StablecoinOperation`. A single merged (flat) shape so the field is unambiguously deserializable regardless of operation type: `accountId` identifies the receiving account (its `ExternalAccount:` / `InternalAccount:` prefix disambiguates external vs Grid-managed), and `rail` is present for burn (fiat payout) destinations and absent for mint destinations. required: - accountId properties: accountId: type: string description: >- Grid account that received the funds. An `ExternalAccount:` id for external destinations or an `InternalAccount:` id for Grid-managed destinations. example: ExternalAccount:019542f5-b3e7-1d02-0000-000000000205 rail: type: string enum: - WIRE - ACH_CREDIT - SAME_DAY_ACH_CREDIT - RTP_CREDIT description: Fiat payout rail, present for burn (fiat redemption) destinations. StablecoinEstimatedDelivery: type: object description: >- Static rail timing estimate for fiat redemption delivery. This is guidance, not a guaranteed arrival time. additionalProperties: true properties: rail: type: string description: Fiat payout rail the estimate applies to. example: ACH_CREDIT amount: type: string pattern: ^[0-9]+$ description: >- Estimated delivery amount in the smallest unit of `currency` (e.g. cents for USD). example: '100' currency: type: string description: ISO 4217 currency code of the fiat payout. example: USD timing: type: string description: Human-readable rail timing estimate. example: 1-3 business days example: rail: ACH_CREDIT amount: '100' currency: USD timing: 1-3 business days securitySchemes: BasicAuth: type: http scheme: basic description: >- API token authentication using format `:` AgentAuth: type: http scheme: bearer description: >- Bearer token authentication for agent-scoped endpoints. The token is the `accessToken` returned when redeeming a device code via `POST /agents/device-codes/{code}/redeem`. Agent credentials are user-scoped: all requests are automatically bound to the agent's associated customer and subject to the agent's policy. ````