# Execute pending order

Executes a pending order using client-provided signatures for the unsigned payloads

Endpoint: POST /orders/{id}/execute
Version: 1.0.0
Security: bearerAuth

## Path parameters:

  - `id` (string, required)
    Order ID

## Request fields (application/json):

  - `signatures` (array, required)
    Signed stamps for the unsigned payloads, in the same order as the payloads returned by the create endpoint. Each signature corresponds to one payload.

  - `auth_type` (string, required)
    The authentication method used to sign transaction payloads.
*  — Signed using a passkey (WebAuthn/FIDO2 credential) via the browser.
*  — Signed using an API key. Suitable for programmatic/headless access.
    Enum: "web_authn", "api_key"

## Response 200 fields (application/json):

  - `status` (string)
    The current status of the order.
*  — Order has been created but not yet submitted. For DeFi orders, the client must sign the returned payloads and call the execute endpoint. For CeFi buy orders with insufficient balance, a funding bridge is prepared first.
*  — Order has been submitted but is not yet confirmed by the CeFi exchange or on-chain.
*  — Order was accepted by the CeFi exchange and is open for trading. Applies to limit orders that are working in the order book.
*  — A cancellation request has been sent to the CeFi exchange and is awaiting confirmation.
*  — Order has been fully executed. For CeFi orders this means the CeFi exchange reported a fill; for DeFi orders the on-chain swap was confirmed.
*  — Order was successfully canceled via a cancel request or by exchange/market conditions.
*  — Order was rejected by the CeFi exchange or DeFi execution failed (e.g. on-chain transaction reverted, balance check failed).
    Enum: "initialized", "pending", "cancel_pending", "complete", "canceled", "active", "failed"

## Response 400 fields (application/json):

  - `message` (string)
    Error message

## Response 401 fields (application/json):

  - `message` (string)
    Error message

## Response 403 fields (application/json):

  - `message` (string)
    Error message

## Response 404 fields (application/json):

  - `message` (string)
    Error message

## Response 409 fields (application/json):

  - `message` (string)
    Error message

## Response 500 fields (application/json):

  - `message` (string)
    Error message

## Response 503 fields (application/json):

  - `message` (string)
    Error message