Skip to main content
Production users should expect rate and service-protection limits. Teams planning sustained high-volume traffic should contact [email protected] so we can coordinate limits and support.

​
Policy limits

The API applies these limits automatically: If a requested deadline exceeds the max, the server may clamp the returned order deadline. Always sign the deadline in the built order response — see place orders.

​
Error format

Errors are returned as:
Common statuses: On 401, re-run the authentication flow and retry with a fresh JWT.

​
Production checklist

Before placing sustained mainnet flow, confirm your client can:
  • re-authenticate after 401 responses
  • reconnect WebSockets with backoff
  • rebuild local books from snapshot plus buffered diffs
  • treat cancellation 202 responses as acknowledgements, not final states
  • keep all uint256 values as strings through signing and saving
  • use the order book token decimals when converting raw amounts for display or order sizing
  • store JWTs and private keys only in server-side secret storage
  • monitor open order count, deadlines, and rate-limit responses
  • reconcile user events with GET /orders/:orderId/history after reconnects

​
Next steps

Authentication

Handle JWT expiry and 401 renewals with the challenge and verify flow.

WebSockets

Implement reconnects, backoff, and snapshot-plus-diff book rebuilds.

Orders

Review deadline handling, batch caps, and cancellation finality in context.

Orderbook API overview

Return to the integration flow and the full endpoint summary.