Overview
Welcome to the Rocky Perpetual Contracts API reference. The structure of this section follows the industry-standard USD-margined perpetual futures conventions, so existing integrations port over with minimal changes.
Two HTTP surfaces
| Surface | Path prefix | Audience | Auth |
|---|---|---|---|
| Web v1 | /v1/* | Browser front-end and wallet-bound integrations | Authorization: Bearer <session_token> obtained from POST /v1/wallet/verify |
| FAPI | /fapi/v1/*, /fapi/v2/* | Programmatic clients / bots (industry-standard) | X-MBX-APIKEY header + HMAC-SHA256 (or Ed25519) signature |
Base URLs
| Environment | Base URL |
|---|---|
| Devnet | https://api.rocky.exchange |
| Mainnet | https://api.rocky.exchange |
How to read this section
Every endpoint below carries a status:
- Implemented — Rocky serves this endpoint today; the page documents the request, response, and quirks.
- Not yet implemented (空缺) — Rocky has not yet added this endpoint. The page records the external method/path and the planned scope. Mostly these stubs exist so SDK developers can see the gap at a glance.
When a Rocky endpoint differs from the standard shape (different path, fewer fields), the page calls that out near the bottom.