Skip to main content
The Exchange endpoints are the write side of the Intention REST API. They accept signed actions — orders, modifications, cancels, and batches — and route them into the matching engine. This page will document each endpoint, its request payload, its signing requirements, and its response shape.
Status: not yet published. The Exchange endpoints will be released alongside the public testnet. Until then, treat the descriptions below as planning documentation.

​
What this page will contain

When the API ships, this page will list:
  • Place order. Submit a new order with a full set of optional flags — time-in-force, post-only, reduce-only, scale, TWAP child, attached TP/SL.
  • Modify order. Update the price or size of a resting order without losing queue position when the protocol allows it. See Modify orders.
  • Cancel order. Cancel a single resting order. Cancels are sequenced ahead of new placements within the same block; see Transaction sequencing.
  • Batch. Submit multiple actions in a single signed envelope — useful for rapid quote updates by market makers.
  • Margin actions. Add or remove margin from isolated positions; see Add margin.

​
Signing and nonces

Every Exchange action is a signed action. Read signing and nonces before integrating. Misuse of nonces under concurrency is the most common source of self-inflicted errors at the write endpoints.

​
Rate limits and errors

Write endpoints have their own rate limits and a dedicated set of errors. Order-flow rate limits are tighter than read limits and may differ per market. For early integration questions, email contact@intention.xyz.