Trading
Trading endpoints let your backend place and manage orders on behalf of segregated end-user accounts.
Capabilities
| Capability | Description |
|---|---|
| Place order | Market / limit (and other enabled time-in-force modes); category: linear for USDT perps, spot where enabled |
| Cancel / amend | Cancel by id; amend where the venue supports it |
| Open orders | List working orders for an account |
| Order history | Historical orders for reporting and support |
| Positions | Open positions, unrealized PnL fields, leverage (derivatives) |
| Set leverage / margin mode | Where enabled for the contract type |
Client order ids
Send your own client order id on placement so retries stay idempotent. Store the venue order id returned in the acknowledgment for cancels and support.
Risk and filters
Orders must respect instrument filters (min qty, tick size, notional). Surface venue reject messages to your users without exposing internal error codes that reveal infrastructure.
Example (illustrative)
POST /v1/trade/orders
Authorization: Bearer <token>
Content-Type: application/json
{
"symbol": "BTCUSDT",
"side": "Buy",
"orderType": "Limit",
"qty": "0.01",
"price": "60000",
"category": "linear",
"clientOrderId": "partner-order-123"
}
Out of scope for public docs
- Internal mirror / counter-copy control planes
- Operator-only force actions
- Raw exchange master-account tooling