Skip to main content
Private REST operations are account-scoped (addresses and parameters in the path/body per OpenAPI) or state-changing (signed transactions in the request body). Use API management for your API key and configure it in the Rust or Python SDK to sign submits—keys are not passed as REST auth headers. See Authentication and SDKs and examples. In OpenAPI, these routes are tagged Account, Trading, Vault and bridge, and Faucet (testnet): Market-wide live reads (instruments, fees, expirations) live under Public REST-API. Historical fills, order history, portfolio, vault history, and candles live under Indexer REST-API. Trading flows are often asynchronous; confirm outcomes with WebSocket subscriptions and follow-up reads where appropriate. Use Swagger UI for interactive calls. The live contract is openapi.json for codegen and validation.