REST
The Public API provides REST endpoints to everyone. No authentication or credentials are required. You must agree to the Figure Markets Terms of Service and Privacy Notice before use.
For near real-time market data, use the WebSocket API instead of polling. That reduces request volume and helps you stay within rate limits.
Base path (main domain)
- UAT:
https://www.figuremarkets.dev/service-hft-exchange - Production:
https://www.figuremarkets.com/service-hft-exchange
Paths in the section guides are relative to that base (for example GET /api/v1/markets, GET /api/v2/...). Full URL = REST base + path. No authentication.
Sections
Public REST endpoints are grouped by section and map to the Public API OpenAPI spec (combined; includes market data and lending). For request/response schemas, use the Public API spec.
All endpoints are read-only.
Versioning: We do not remove fields or change types for existing keys within a given API version; we may add new fields without a version bump. See API versioning for the full policy.
| Section | What it covers | Guide |
|---|---|---|
| Assets | Assets, asset by name, price, blockchains. | Assets |
| Markets | List markets, get market, order book, candles. | Markets |
| Trades | Get trades by market. | Trades |
| Lending | Leverage pools and offers (public lending data; Democratized Prime). | Lending |
Rate limits and best practices
Public REST is rate limited at the gateway (often per IP). The same general rules apply to Trader and Partner REST as well: treat 429 with backoff, keep request rates reasonable, and prefer streaming where we offer it.
Full guidance (429 handling, WebSocket vs polling, Trader/Partner notes): Rate limits and best practices.
For public market data specifically, prefer WebSocket streams over frequent REST polling.
Example: first steps (public)
- Markets — List markets via Markets:
GET /api/v1/markets. Use thesymbolin REST calls or WebSocket subscriptions. - Real-time updates — Use the WebSocket API to subscribe to MARKET, ORDER_BOOK, TRADES, or CANDLES for live data.
- Lending data (optional) — Use Lending for pool details and offers when building lending flows.
For full request/response shapes and error handling, see the Public API spec.