API overview
Partners integrate against HTTP APIs (and where applicable WebSocket market/private streams) for market data, accounts, and trading.
This documentation describes capabilities and resource shapes at a product level. It intentionally omits internal authentication bypasses, encryption key formats, infrastructure endpoints, and operator-only recovery tools.
Capability map
| Area | What you do | Doc |
|---|---|---|
| Authentication | Obtain and refresh partner / user sessions | Authentication |
| Market data | Instruments, tickers, order books, candles | Market data |
| Trading | Place, amend, cancel; read orders and positions | Trading |
| Accounts | Balances, sub-accounts, funding status (high level) | Accounts |
Design principles
- Backend-first - keep long-lived credentials on your servers
- Least privilege - separate read-only market credentials from trading credentials when issued
- Idempotent client order ids - support safe retries on place/cancel
- Environment isolation - staging and production credentials never mix
Related public surfaces
| Surface | Role | URL |
|---|---|---|
| Institutional landing | Commercial entry | https://institutional.eterna.exchange |
| Retail app | Reference UX for live markets | https://app.eterna.exchange |
| Advanced trade API docs | Separate advanced key product | https://api2-docs.eterna.exchange |
Credential issuance and base URLs for your tenant are provided during onboarding.