---
title: "Amend Order Command"
method: POST
path: "/v2/command#amend"
tags: ["orders"]
---

# Amend Order Command

`POST /v2/command#amend`

## Request

- Base URL: `https://api.exchange.bullish.com/trading-api`
- URL: `https://api.exchange.bullish.com/trading-api/v2/command#amend`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/bullish/apis/bullish-trading-api/docs/v2/command%23amend/post.ts> (a function with typed inputs; its response is checked against the schema)

Ability to amend the `price`, `quantity` and `type` (i.e. change from Taker Only to Maker Only and vice versa) on GTC Limit orders. It can be applied only to open orders (`quantityFilled=0` and `status=OPEN`). For Auction Limit Orders (LOC), only `price` can be amended. Auction Market Orders (MOC) do not support amendment.

Submits a command to the trading engine to amend an order. A successful response indicates that the command entry was acknowledged 
but does not indicate that the command was executed. 

This endpoint uses the [signing format](/rest/authentication#signing-format) which does not require strict field 
ordering and addition of null fields in the request body. Quantities and prices does not require strict precision. 
E.g. for asset precision of 4 - `100`, `100.0`, `100.00`, `100.000` and `100.0000` are all accepted.

Requires
- [bearer token](/rest/authentication#add-authenticated-request-header) in authorization header

**Ratelimited:** `True`. Higher tiers of rate limits available by providing the `BX-RATELIMIT-TOKEN` request header.

## Headers

- `BX-SIGNATURE` string, required
- `BX-TIMESTAMP` string, required
- `BX-NONCE` string, required
- `BX-NONCE-WINDOW-ENABLED` 'false' | 'true'

## Request body

- AmendOrderCommandV1
  - `commandType` 'V1AmendOrder', required: The command type, it must be 'V1AmendOrder'
  - `orderId` string
  - `symbol` string, required: market symbol. E.g. `BTCUSDC`
  - `type` string: order type can have the following string values `"LIMIT"`, `"POST_ONLY"`
  - `price` string: see [asset value](/rest/general/price-quantity-precision) format
  - `clientOrderId` string: unique numeric identifier generated on the client side expressed as a string value
  - `quantity` string: see [asset value](/rest/general/price-quantity-precision) format
  - `tradingAccountId` string, required: unique trading account ID

## Response `200`

Status OK. This means a command was successfully acknowledged.

- AmendOrderCommandResponseV1
  - `commandType` 'V1AmendOrder', required: The command type
  - `message` string, required: message
  - `requestId` string, required
  - `orderId` string, required
  - `clientOrderId` string: Will be updated as part of a successful order amendment

## Other responses

- `400`: Bad Request For example, sending a request with the `BX-SIGNATURE` header missing will result in the following response:
- `401`: Not Authenticated
- `403`: Access Forbidden
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/bullish/apis/bullish-trading-api.md) - [All operations](https://skmtc.dev/bullish/apis/bullish-trading-api/llms.txt) - [OpenAPI document](https://skmtc.dev/bullish/apis/bullish-trading-api/revisions/df5d69ccedcf?raw)