> 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.

# Developer Overview

The Developer section is for backend engineers and platform teams integrating directly with 6MM APIs. It explains the conventions, security model, REST resources, streaming channels, and operational checks needed before production use.

<h2 id="recommended-integration-path">
  Recommended integration path
</h2>

Understand the API access model and recommended connection sequence.

Review base URLs, timestamps, numeric fields, and response format.

Prepare JWT access, API keys, and HMAC signing.

Explore account, order, position, and market data endpoints.

<h2 id="documentation-areas">
  Documentation areas
</h2>

| Area                        | What it covers                                                            |
| --------------------------- | ------------------------------------------------------------------------- |
| Integration setup           | Service addresses, request conventions, response shape, and access modes. |
| Authentication & security   | JWT, API Key permissions, HMAC signing, replay protection, and time sync. |
| REST API                    | Public endpoints, user/account data, orders, positions, and market data.  |
| WebSocket                   | Connection lifecycle, public market streams, and private user streams.    |
| Reference & troubleshooting | Enums, error codes, and practical integration recommendations.            |

<h2 id="production-checklist">
  Production checklist
</h2>

* Store API secrets only on the backend.
* Sync server time before signed requests.
* Treat all numeric precision fields as strings unless a page explicitly says otherwise.
* Use idempotency, request IDs, and structured logs around order flows.
* Subscribe to WebSocket streams for state that must stay current in operational systems.
* Review error codes and retry behavior before launch.