Trading (low-latency)
The Trader API provides low-latency trading for API traders over REST.
Use the same Trader API bearer token as for the standard API, but HTTP requests go to a dedicated host:
trade.figuremarkets.com.
Important: The low latency API is deployed to the Southeast Asia region. In order to take full advantage, it is recommended that any application using this API be deployed to the same region.
Obtain the token first — see Authentication — Obtaining an access token.
Figure Markets runs a gateway in front of the trading service. If trading is deployed in another region, Figure Markets will tell you which gateway host to use.
REST mapping
Low-latency trading exposes one HTTP method per operation: POST to /api/v1/{operation} (snake_case path
segment), for example POST /api/v1/insert_order. Send a JSON body (Content-Type: application/json) shaped like the
OpenAPI schema for that operation; field names are camelCase in JSON (for example order_qty, time_in_force,
start_time).
Unary operations return application/json. Streaming operations (subscriptions and CSV download streams) use *
newline-delimited JSON* (application/x-ndjson) as described per operation in
the Trader API spec (low-latency).
How to trade
| Step | Doc |
|---|---|
| Account | Account — One user, one account per key. Resolve it once and use it for all requests. |
| Balances | Balances — List balances so you know how much you can trade. |
| Markets | Markets — Discover symbols/instruments; order book and pricing (spec endpoints and Public API). |
| Orders | Orders — Insert, cancel, replace; subscribe to working orders; search and download history. |
YLDS (stablecoin) orders are not part of the low-latency API. For those, use Orders on the Standard API.
For full request/response shapes, use the Trader API spec (low-latency).
For real-time public data use the Public WebSocket.
Next steps
| Step | Doc |
|---|---|
| Get and use Trader API token | Authentication |
| Margin, lending, YLDS, standard Orders | Standard API |