Integration overview
Partners integrate against documented HTTP and WebSocket surfaces. Credentials are issued per environment during onboarding. This page stays at the commercial and architectural level on purpose.
Building blocks
- Partner identity - your organization and brand configuration
- End-user accounts - segregated sub-accounts under your partner umbrella
- Market data - instruments, tickers, order books, and candles
- Trading - order placement, cancellation, positions, and balances
- Admin console - operator tooling for your team (see Admin)
Environments
| Environment | Purpose |
|---|---|
| Staging | Integration testing with non-production credentials |
| Production | Live users and fee share |
Exact hostnames and credential delivery are shared during onboarding - not published as shared secrets in public docs.
Security expectations (partner side)
- Store API credentials in your secret manager; rotate on a schedule
- Call APIs from your backend; never embed long-lived secrets in client apps
- Prefer short-lived user session tokens for browser and mobile surfaces
- Restrict admin operator access with least-privilege roles
Internal encryption material, exchange master keys, and infrastructure credentials are never shared with partners and are not documented here.