Skip to main content
Public REST operations do not require an API key in the HTTP request. Use them to discover instruments, feeds, fees, leverage limits, funding-related history, and other market-wide data before you move on to account-scoped reads or SDK-signed writes. In the generated OpenAPI document, these routes are tagged Service and Market data:
TagTypical use
ServiceHealth or availability-style checks.
Market dataInstruments, candles, fees, leverage limits, funding-style events, fill volumes by instrument type, and similar reads.
For account balances, positions, orders, vaults, transaction submission, and testnet faucet calls, use Private REST-API. When you want to try requests against the live beta stack, use Swagger UI. The same contract is published at openapi.json; this documentation site builds its REST pages from the copy in specs/openapi.json (summaries, parameter tables, and examples are maintained there — run node scripts/enrich-openapi-rest-docs.mjs after updating the spec).