Skip to main content

Get Cross History Orders

Get Cross History Orders

Rate limit:10 req/sec/UID

Description

HTTP Request

  • GET /api/v2/margin/crossed/history-orders
Request Example
curl "https://api.bitget.com/api/v2/margin/crossed/history-orders?symbol=BTCUSDT&limit=20&startTime=1779235200000&endTime=1779840000000" \
-H "ACCESS-KEY:*******" \
-H "ACCESS-SIGN:*******" \
-H "ACCESS-PASSPHRASE:*****" \
-H "ACCESS-TIMESTAMP:1659076670000" \
-H "locale:en-US" \
-H "Content-Type: application/json" \

Request Parameters

ParameterTypeRequiredDescription
symbolStringYesTrading pairs, like BTCUSDT
orderIdStringNoOrder ID
enterPointSourceStringNoOrder source
WEB: Orders created on the website
API: Orders created on API
SYS: System managed orders, usually generated by forced liquidation logic
ANDROID: Orders created on the Android app
IOS: Orders created on the iOS app
clientOidStringNoClient customized ID
startTimeStringYesStart time, Unix millisecond timestamp
endTimeStringNoEnd time, Unix millisecond timestamp
Maximum interval between start time and end time is 90 days
limitStringNoNumber of quiries
Default: 100, maximum: 500
idLessThanStringNoFor turning pages
It's not needed in the first query. When querying data in the second page and the data beyond, the last endId returned in the last query is used, and the result will return data with a value less than this one; the query response time will be shortened.
Response Example
{
"code": "00000",
"msg": "success",
"requestTime": 1695636829522,
"data": {
"orderList": [
{
"orderId": "121211212122",
"symbol": "BTCUSDT",
"orderType": "limit",
"enterPointSource": "API",
"clientOid": "myClientOid001",
"loanType": "normal",
"price": "32111",
"side": "buy",
"status": "filled",
"baseSize": "0.01",
"quoteSize": "1000",
"priceAvg": "32111",
"size": "0.01",
"amount": "1000",
"force": "gtc",
"cTime": "1695629859821",
"uTime": "1695629890839"
}
],
"maxId": "121211212122",
"minId": "121211212122"
}
}

Response Parameters

ParameterTypeDescription
orderListListOrder list
>symbolStringTrading pair
>orderIdStringOrder ID
>clientOidStringClient customized ID
>sizeStringFilled quantity
>priceAvgStringOrder price
>amountStringFilled volume
>forceStringTime in force
gtc: normal limit order, good till canceled
post_only: Post only
fok: Fill or kill
ioc: Immediate or cancel
>priceStringOrder price
>enterPointSourceStringOrder source
WEB: Orders created on the website
API: Orders created on API
SYS: System managed orders, usually generated by forced liquidation logic
ANDROID: Orders created on the Android app
IOS: Orders created on the iOS app
>statusStringOrder status
live: New order
partially_fill: Partially filled
filled: Fully filled
cancelled: Cancelled
reject: Rejected
>sideStringDirection
sell: Sell
buy: Buy
liquidation-buy: Settlement – buy
liquidation-sell: Settlement – sell
systemRepay-buy: Repay by system – buy
systemRepay-selll: Repay by system – sell
>baseSizeStringQuantity of the base currency
>quoteSizeStringQuantity of the quote currency
>orderTypeStringOrder type
limit: limit price
market: market price
>cTimeStringCreation time
>uTimeStringUpdated time
>loanTypeStringMargin order model
normal: place a normal order
autoLoan place an order with auto-borrow
autoRepay place an order with auto-repay
autoLoanAndRepay place an order with auto-borrow and auto-repay
maxIdStringMax ID of current search result
minIdStringMin ID of current search result, use: idLessThan=minId in the next query

How was your Reading Experience with us?