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

# Get order approval

> Returns the pending embedded-wallet approval for an order, if one is awaiting the
owner's signature. A non-custodial (embedded) wallet can't be signed by Etherfuse
alone: we build the transaction and the partner-held owner key must approve it.

The `approvalMessage` bytes are built fresh on each read so they are current when
signed. Sign them with the owner's key and submit the signature to
`POST /ramp/order/{order_id}/approvals`.



## OpenAPI

````yaml /openapi.json get /ramp/order/{order_id}/approvals
openapi: 3.1.0
info:
  title: Etherfuse FX API
  description: Partner-facing ramp API for onramps, offramps, swaps, and KYC.
  license:
    name: Proprietary
  version: 1.0.0
servers:
  - url: https://api.sand.etherfuse.com
    description: Sandbox
security:
  - ApiKeyAuth: []
tags:
  - name: Authentication
    description: >-
      Partner JWT authentication — exchange a JWT for an access token, or launch
      a user into the app.
  - name: Lookup
    description: >-
      Public reference data: exchange rates, stablebonds, bond costs, country
      codes.
  - name: Assets
    description: Rampable stablecoins and stablebonds available per blockchain.
  - name: Onboarding
    description: Hosted and programmatic customer onboarding.
  - name: Bank Accounts
    description: Register and retrieve customer bank accounts.
  - name: Quotes
    description: Price quotes for onramps, offramps, and swaps.
  - name: Orders
    description: Create, track, and manage ramp orders.
  - name: Swaps
    description: Crypto-to-crypto swaps.
  - name: Sponsored
    description: Token approvals for sponsored (gasless) offramps.
  - name: Customers
    description: Customer (child-organization) records.
  - name: Wallets
    description: Register and manage customer wallets.
  - name: KYC
    description: Submit and check customer KYC status.
  - name: Webhooks
    description: Event notification subscriptions.
  - name: Organizations
    description: Organization identity, child orgs, and partner fees.
paths:
  /ramp/order/{order_id}/approvals:
    get:
      tags:
        - Orders
      summary: Get order approval
      description: >-
        Returns the pending embedded-wallet approval for an order, if one is
        awaiting the

        owner's signature. A non-custodial (embedded) wallet can't be signed by
        Etherfuse

        alone: we build the transaction and the partner-held owner key must
        approve it.


        The `approvalMessage` bytes are built fresh on each read so they are
        current when

        signed. Sign them with the owner's key and submit the signature to

        `POST /ramp/order/{order_id}/approvals`.
      operationId: get_order_approvals
      parameters:
        - name: order_id
          in: path
          description: The order ID
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: The pending approval packet
          content:
            application/json:
              schema:
                type: object
                required:
                  - approvalMessageId
                  - approvalMessage
                properties:
                  approvalMessageId:
                    type: string
                    format: uuid
                    description: >-
                      Identifies the proposal being approved. Echoed back on
                      submit so a superseded proposal (re-proposed on expiry) is
                      rejected as stale.
                  approvalMessage:
                    type: string
                    description: >-
                      The exact bytes the owner signs with their key. Built
                      fresh on each read so the request is current when signed;
                      submitted back verbatim alongside the signature.
                  summary:
                    type: string
                    description: >-
                      Human-readable description of what is being approved.
                      Present only when set.
        '404':
          description: >-
            No pending approval for this order (or order not found / not visible
            to your API key)
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: API key sent in the Authorization header.

````