1 min read

The 4rho API

4rho exposes a full REST + WebSocket API. The reference documentation lives at /help/api and covers:

  • Authentication — HMAC-signed API keys (recommended for bots) and JWT bearer tokens (browser sessions).
  • Order placement — single, batch, cancel, amend, cancel-replace, GTC / GTD / IOC / FOK time-in-force, post-only, self-trade prevention.
  • Market data — order book snapshots, BBO, spread, midpoint, tick size, server time.
  • User data — positions, orders, trades, fund movements, redeemable positions, fee rates.
  • Real-time — WebSocket channels for trades, book deltas, BBO, fills, and order status.
  • EIP-712 signing — sign orders for on-chain settlement, with ethers.js v6 and web3.py examples.
  • Errors and rate limits.

If you want to build trading bots, market makers, or analytics on top of 4rho, the API is the path.

Quick start

# Public market data (no auth)
curl https://api.4rho.com/v1/markets

# Server time (use this to sync your HMAC clock)
curl https://api.4rho.com/v1/time

For authenticated endpoints, you'll need an API key. They're issued manually right now — open a support ticket with your use case and expected request volume to request one.

Read the full reference

Open the API reference →

You'll find rate limits, scopes, request schemas, response examples, and a fully working signing example in Python and TypeScript.

Was this article helpful?

Your feedback helps us improve our docs.