Skip to main content

Batch Modify Orders

Batch Modify Orders

Description​

tip

The ACK response only indicates that the request has been successfully accepted. Please use the WebSocket order push channel to confirm the actual order status after modification.

  • Supports batch order modification via API, allowing simultaneous submission of multiple orders across different trading pairs (limited to orders within the same business line).
  • Each request supports modification of up to 20 orders.
  • Supports continuous order modification, meaning additional modification requests can be submitted before the previous modification request is completed. A maximum of 5 consecutive modification requests for in-progress orders can be submitted, and the matching engine will process the modification requests in sequence.
  • Within the same batch of modification requests, each order can only appear once.
  • Fully unfilled orders can have their price and quantity modified.
  • Partially filled orders can have their price and quantity modified (the modified quantity cannot be less than the already filled quantity).
  • Modification of reduce-only orders is not supported.
  • If the autoCancel parameter is set to yes and the order modification fails, the original order will be automatically canceled. Modification failure typically occurs in the following two scenarios:
    • The modified price triggers immediate execution, causing the postOnly order to be canceled
    • The new order quantity is less than or equal to the already filled quantity
  • Isolated margin mode is not supported for batch order modification.

HTTP Request​

  • POST /api/v3/trade/batch-modify-order
  • Rate limit: 10/sec/UID
  • Permission: UTA trade
Request
curl -X POST "https://api.bitget.com/api/v3/trade/batch-modify-order" \
-H "ACCESS-KEY:your apiKey" \
-H "ACCESS-SIGN:*" \
-H "ACCESS-PASSPHRASE:*" \
-H "ACCESS-TIMESTAMP:1659076670000" \
-H "locale:zh-CN" \
-H "Content-Type: application/json" \
-d '[{ "orderId": "1","qty": "123", "price": "123", "autoCancel": "no", "symbol": "BTCUSDT", "category": "USDT-FUTURES" },{ "orderId": "2","qty": "123", "price": "123", "autoCancel": "no", "symbol": "ETHUSDT", "category": "USDT-FUTURES" }]'

Request Parameters​

ParametersTypeRequiredDescription
orderIdStringNoOrder ID
Either orderId or clientOid must be provided
If both orderId and clientOid are provided simultaneously, orderId takes higher priority
clientOidStringNoClient order ID
Must match the regular expression ^[\.A-Z\:/a-z0-9_-]{1,32}$, i.e. 1 to 32 characters, consisting of periods (.), uppercase and lowercase letters, colons (:), forward slashes (/), digits, underscores (_), and hyphens (-)
Either orderId or clientOid must be provided
If both orderId and clientOid are provided simultaneously, orderId takes higher priority
requestIdNumberNoCustom request ID to identify this modify order request
Maximum length: 32 characters
Special characters are not supported
Uniqueness is not validated
qtyStringNoOrder quantity
Base coin
priceStringNoOrder price
autoCancelStringNoWill the original order be canceled if the order modification fails
yes: Cancel
no: Not cancel (default)
When set to yes: if the matching engine fails to modify the order, the order is cancelled immediately; after cancellation, the counter will reject any further modification requests for that order (including in-flight and new requests).
symbolStringYesSymbol name
e.g.,BTCUSDT
categoryStringYesProduct type
SPOT Spot trading
MARGIN Margin trading
USDT-FUTURES USDT futures
COIN-FUTURES Coin-M futures
USDC-FUTURES USDC futures
Response
{
"code": "00000",
"data": [
{
"orderId": "1",
"clientOid": "12312"
},
{
"orderId": "2",
"clientOid": "2321"
}
],
"msg": "success",
"requestTime": 1627293504612
}

Response Parameters​

ParameterTypeComments
orderIdStringOrder ID
clientOidStringClient order ID

How was your Reading Experience with us?

★
★
★
★
â˜