Properties
| Name | Type | Description |
|---|---|---|
| serialId | integer | Monotonic sequence identifier for this trade record. |
| tradeId | string | Unique trade identifier. |
| orderId | string | Identifier of the order this trade was executed against. |
| clOrderId | string | Client-supplied order identifier of the originating order. |
| symbol | string | Trading pair, formatted as BASE-QUOTE (e.g. BTC-USDT). |
| base | string | Base currency of the trading pair. |
| quote | string | Quote currency of the trading pair. |
| orderSide | string | Order side: BUY or SELL. |
| orderType | integer | Numeric order-type code of the originating order (limit, market, peg, TWAP). |
| triggerType | integer | Numeric trigger order-type code (stop-loss, take-profit, stop-loss-limit, or take-profit-limit). Only meaningful when the originating order was a trigger order. |
| triggerPrice | number | Trigger price of the originating order. Only meaningful when the originating order was a trigger order. |
| price | number | Execution price of this trade. |
| size | number | Original order size of the originating order. |
| filledSize | number | Amount filled by this trade, in base currency. |
| feeCurrency | string | Currency in which the trading fee was charged. |
| feeAmount | number | Trading fee amount charged for this trade, in feeCurrency. |
| timestamp | integer | Trade execution timestamp in Unix epoch milliseconds. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/btse/main/json-schema/btse-trade-history-resp-schema.json",
"title": "TradeHistoryResp",
"x-generated": "2026-10-13",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/btse-spot-openapi.yml#/components/schemas/TradeHistoryResp",
"type": "object",
"properties": {
"serialId": {
"type": "integer",
"format": "int64",
"description": "Monotonic sequence identifier for this trade record."
},
"tradeId": {
"type": "string",
"description": "Unique trade identifier."
},
"orderId": {
"type": "string",
"description": "Identifier of the order this trade was executed against."
},
"clOrderId": {
"type": "string",
"description": "Client-supplied order identifier of the originating order."
},
"symbol": {
"type": "string",
"description": "Trading pair, formatted as BASE-QUOTE (e.g. BTC-USDT)."
},
"base": {
"type": "string",
"description": "Base currency of the trading pair."
},
"quote": {
"type": "string",
"description": "Quote currency of the trading pair."
},
"orderSide": {
"type": "string",
"description": "Order side: BUY or SELL."
},
"orderType": {
"type": "integer",
"format": "int32",
"description": "Numeric order-type code of the originating order (limit, market, peg, TWAP)."
},
"triggerType": {
"type": "integer",
"format": "int32",
"description": "Numeric trigger order-type code (stop-loss, take-profit, stop-loss-limit, or take-profit-limit). Only meaningful when the originating order was a trigger order."
},
"triggerPrice": {
"type": "number",
"format": "double",
"description": "Trigger price of the originating order. Only meaningful when the originating order was a trigger order."
},
"price": {
"type": "number",
"format": "double",
"description": "Execution price of this trade."
},
"size": {
"type": "number",
"format": "double",
"description": "Original order size of the originating order."
},
"filledSize": {
"type": "number",
"format": "double",
"description": "Amount filled by this trade, in base currency."
},
"feeCurrency": {
"type": "string",
"description": "Currency in which the trading fee was charged."
},
"feeAmount": {
"type": "number",
"format": "double",
"description": "Trading fee amount charged for this trade, in feeCurrency."
},
"timestamp": {
"type": "integer",
"format": "int64",
"description": "Trade execution timestamp in Unix epoch milliseconds."
}
}
}
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/btse-trade-history-resp"
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.