BigONE · Schema
UserTrade
A trade execution record from the user's perspective.
CompanyCryptocurrencyExchangeTradingDerivativesWalletsMarket Data
Properties
| Name | Type | Description |
|---|---|---|
| id | integer | The unique trade ID. |
| asset_pair_name | string | The asset pair name. |
| price | string | The execution price. |
| amount | string | The traded amount (base asset quantity). |
| taker_side | string | The side of the taker (the order that matched). ASK = taker sold, BID = taker bought. |
| side | string | The side from the maker's perspective. SELF_TRADING indicates both sides of the trade were from the same user. |
| maker_order_id | integernull | The order ID of the maker (the liquidity provider). Null if the maker order was not found. |
| taker_order_id | integernull | The order ID of the taker (the liquidity taker). |
| maker_fee | stringnull | The fee paid by the maker (negative values indicate rebates). Null if the user was the taker. |
| taker_fee | stringnull | The fee paid by the taker. Null if the user was the maker. |
| inserted_at | string | The timestamp when the trade was recorded (RFC3339 with millisecond precision). |
| created_at | string | Alias for inserted_at (same value). |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/bigone/main/json-schema/bigone-user-trade-schema.json",
"title": "UserTrade",
"description": "A trade execution record from the user's perspective.",
"x-generated": "2026-10-13",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/bigone-spot-openapi.yml#/components/schemas/UserTrade",
"type": "object",
"properties": {
"id": {
"type": "integer",
"format": "int64",
"description": "The unique trade ID."
},
"asset_pair_name": {
"type": "string",
"description": "The asset pair name."
},
"price": {
"type": "string",
"description": "The execution price."
},
"amount": {
"type": "string",
"description": "The traded amount (base asset quantity)."
},
"taker_side": {
"type": "string",
"description": "The side of the taker (the order that matched). ASK = taker sold, BID = taker bought.",
"enum": [
"ASK",
"BID"
]
},
"side": {
"type": "string",
"description": "The side from the maker's perspective. SELF_TRADING indicates both sides of the trade were from the same user.",
"enum": [
"ASK",
"BID",
"SELF_TRADING"
]
},
"maker_order_id": {
"type": [
"integer",
"null"
],
"format": "int64",
"description": "The order ID of the maker (the liquidity provider). Null if the maker order was not found."
},
"taker_order_id": {
"type": [
"integer",
"null"
],
"format": "int64",
"description": "The order ID of the taker (the liquidity taker)."
},
"maker_fee": {
"type": [
"string",
"null"
],
"description": "The fee paid by the maker (negative values indicate rebates). Null if the user was the taker."
},
"taker_fee": {
"type": [
"string",
"null"
],
"description": "The fee paid by the taker. Null if the user was the maker."
},
"inserted_at": {
"type": "string",
"description": "The timestamp when the trade was recorded (RFC3339 with millisecond precision)."
},
"created_at": {
"type": "string",
"description": "Alias for inserted_at (same value)."
}
}
}
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/bigone-user-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.