---
title: "Accept a quote"
method: POST
path: "/trading/quote/accept"
tags: ["Trading"]
---

# Accept a quote

`POST /trading/quote/accept`

Permissions required: **Execute trades**


Accept a quote by its quoteID and side.

#### Idempotent Requests

This endpoint supports [idempotent requests](#section/Idempotency) so that a quote cannot be accepted twice if an API call was interrupted and is retried. To send an idempotent request, include the `idempotentId` field in the body of the POST request.

## Headers

- `Api-Signature` string, required
- `Api-Timestamp` integer, required

## Request body

- AcceptQuoteRequest
  - `accountId` string, required — The ID of a trading account. This field is used to specify the trading account into which assets should be settled.
  - `allowedSlippage` string — The maximum slippage Anchorage Digital will consider when accepting this order, communicated in terms of actual value (i.e. "0.001" => 10bps). Must be greater than or equal to 0 and less than or equal to 0.002 (20bps). In order to illustrate how this setting works, as an example, we shall consider a commission of 10bps for a quote priced at 10000, and that we are about to accept this quote with an allowedSlippage of "0.0008" (8bps). Then, considering the market has moved away from the quoted price, one of the following two scenarios will be applicable: 1) Best market price within allowedSlippage - fill the order at the spread off the market Best Market Price: 10007 Trade Status: Executed Customer Execution Price: 10017.007 2) Best market price outside of allowedSlippage - reject the order Best Market Price: 10009 Trade Status: Rejected
  - `idempotentId` string, nullable — A client-provided unique ID for idempotent requests (optional). This value must match the one provided to [request quote](#operation/requestQuote).
  - `quoteID` string, required — ID of the quote to trade.
  - `side` 'BUY' | 'SELL', required — Trade side, either "BUY" or "SELL".
  - `vaultID` string — Currently in BETA. The ID of a vault. This optional field is used to specify the vault into which assets should be settled. If provided, the API key must have the following permissions: **Read vault activity**

## Response `200`

Successfully accepted the quote

- AcceptQuoteResponse
  - `data` AcceptQuoteResponseData, required
    - `quoteID` string, required — ID of the quote to trade.
    - `side` 'BUY' | 'SELL', required — Trade side, either "BUY" or "SELL".
    - `tradeID` string — ID of the trade.
    - `tradeStatus` 'PENDING' | 'REJECTED' | 'CANCELED' | 'EXECUTED' | 'SETTLING' | 'SETTLED' | 'PENDINGALLOCATION' | 'ALLOCATED', required — A string describing the status of the given trade * `PENDING` - The trade request has been placed and the trade is pending. * `EXECUTED` - This trade was executed and is waiting customer deposit. * `REJECTED` - This trade was rejected. * `CANCELED` - This trade was canceled by Anchorage Digital's trading team due to client legal/financial problems. * `SETTLING` - Anchorage Digital received the customer's deposit and the trade is in the process of settling. * `SETTLED` - Trade is settled and assets were sent to the customer. * `PENDINGALLOCATION` - Trade is executed and is awaiting client allocation. * `ALLOCATED` - Trade is fully allocated by the client.

## Other responses

- `400` — Bad Request
- `401` — Unauthenticated
- `403` — Forbidden
- `404` — Not Found. The specified quoteID is either invalid or expired.
- `409` — Trade already exists
- `422` — Request exceeds credit limit
- `429` — Too Many Requests
- `500` — Internal Server Error

---

[API](https://skmtc.net/anchorage/apis/anchorage-digital-api-reference.md) · [All operations](https://skmtc.net/anchorage/apis/anchorage-digital-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/anchorage/anchorage-digital-api-reference/revisions/166864b1ec6d/schema)