Environments and Common Conventions

Service Endpoints

Time and Numeric Values

• Unless otherwise specified, time fields are Unix millisecond timestamps.
• Daily statistics, balance snapshots, and trading volume statistics use UTC day boundaries by default.
• Precision-sensitive fields such as amount, price, quantity, and rate are transmitted as strings.
• Large integer IDs such as orderId, conditionId, and strategyId are returned as strings in JSON.

Response Format

Successful response:

1
{
2
  "code": 0,
3
  "message": "success",
4
  "data": {},
5
  "requestId": "req-12345678"
6
}

Error response:

1
{
2
  "code": 1003,
3
  "message": "Invalid token",
4
  "requestId": "req-12345678"
5
}

Notes:

• Business errors usually still return the unified JSON structure. Integrators should check code first.
• Authentication failures may return HTTP 401; rate limiting may return HTTP 429.
• You may send X-Request-ID in the request header. The server will return it as requestId in the response.