> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.6mm.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.6mm.com/_mcp/server.

# Environments and Common Conventions

> Review 6MM API environments and shared conventions for base URLs, timestamps, numeric fields, symbols, request IDs, pagination, and responses.

## Service Endpoints

| Type      | Endpoint              |
| --------- | --------------------- |
| REST API  | `https://api.6mm.com` |
| WebSocket | `wss://ws.6mm.com/ws` |

## 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:

```json
{
  "code": 0,
  "message": "success",
  "data": {},
  "requestId": "req-12345678"
}
```

Error response:

```json
{
  "code": 1003,
  "message": "Invalid token",
  "requestId": "req-12345678"
}
```

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.

## Related documentation

* [Authentication](/developer-api/authentication): choose JWT or API Key signing.
* [Request Signing](/developer-api/request-signing): construct and verify signed requests.
* [REST API](/developer-api/rest-api): apply these conventions to endpoint groups.
* [Error Codes & Troubleshooting](/developer-api/error-codes-and-troubleshooting): diagnose HTTP and business errors.