Skip to main content
In addition to subscriptions, the Intention WebSocket API will expose a low-latency post channel for placing, modifying, and cancelling orders without the overhead of a fresh REST request. The post channel is intended for market makers, latency-sensitive integrations, and clients that already maintain a long-lived WebSocket connection for market data.
Status: not yet published. The post channel protocol 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 document:
  • Action types. Place, modify, cancel, batch, and margin actions sent over the post channel, mirroring the Exchange REST endpoints.
  • Signing. How signed-action envelopes are framed inside WebSocket messages, cross-referenced with signing.
  • Acknowledgements. The shape of post-channel acks, the relationship between ack arrival and block commit, and how clients should reconcile acks with subscription updates.
  • Ordering. How the post channel interacts with transaction sequencing — in particular, the cancel-before-place priority within a single block.
  • Rate limits. Post-channel-specific limits and how they compose with REST limits, cross-referenced with rate limits.
For early integration questions, email contact@intention.xyz.