HitBTC · Schema
trading_HistoryTrade
CompanyCryptocurrencyCryptocurrency ExchangeTradingMarket DataFuturesWallets
Properties
| Name | Type | Description |
|---|---|---|
| id | integer | Trade unique identifier as assigned by the exchange. |
| orderId | integer | Unique order identifier as assigned by the exchange. |
| clientOrderId | string | Unique order identifier as assigned by the trader. |
| symbol | string | Symbol code. |
| side | string | Trade side. |
| quantity | string | Quantity of trade. |
| price | string | Trade price. |
| fee | string | Fee paid for trade. |
| timestamp | string | Trade timestamp. |
| taker | boolean | Liquidity indicator. |
| positionId | integer | Position identifier. |
| pnl | string | Realized profit produced by the trade. |
| otc | booleannull | Flag that indicated whether the trade was performed out the trading venue. |
| liquidation | booleannull | Flag that indicated whether the trade was a close trade. |
| margin_mode | string | Margin mode. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/hitbtc/main/json-schema/hitbtc-trading-history-trade-schema.json",
"title": "trading_HistoryTrade",
"x-generated": "2026-10-13",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/hitbtc-v2-openapi.yml#/components/schemas/trading_HistoryTrade",
"required": [
"id",
"orderId",
"clientOrderId",
"symbol",
"side",
"quantity",
"price",
"fee",
"timestamp",
"taker",
"margin_mode"
],
"type": "object",
"properties": {
"id": {
"type": "integer",
"format": "uint64",
"description": "Trade unique identifier as assigned by the exchange."
},
"orderId": {
"type": "integer",
"format": "uint64",
"description": "Unique order identifier as assigned by the exchange."
},
"clientOrderId": {
"type": "string",
"description": "Unique order identifier as assigned by the trader."
},
"symbol": {
"type": "string",
"description": "Symbol code."
},
"side": {
"type": "string",
"enum": [
"sell",
"buy"
],
"description": "Trade side."
},
"quantity": {
"type": "string",
"description": "Quantity of trade."
},
"price": {
"type": "string",
"description": "Trade price."
},
"fee": {
"type": "string",
"description": "Fee paid for trade."
},
"timestamp": {
"type": "string",
"format": "date-time",
"description": "Trade timestamp."
},
"taker": {
"type": "boolean",
"description": "Liquidity indicator."
},
"positionId": {
"type": "integer",
"format": "uint64",
"description": "Position identifier."
},
"pnl": {
"type": "string",
"description": "Realized profit produced by the trade."
},
"otc": {
"type": [
"boolean",
"null"
],
"description": "Flag that indicated whether the trade was performed out the trading venue."
},
"liquidation": {
"type": [
"boolean",
"null"
],
"description": "Flag that indicated whether the trade was a close trade."
},
"margin_mode": {
"type": "string",
"enum": [
"isolated",
"cross"
],
"description": "Margin mode."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/hitbtc-trading-history-trade"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.