majjha.developers
Open beta

Public beta: activity uses test Dots with no monetary value. There is no money in or out, and interfaces may change before launch.

Market makers

majjha makers quote the same central limit order book as the consumer app. This public guide covers market data, quote hygiene, and monitoring.

Approved beta access

Automated order entry is an approved beta surface. Write schemas, credentials, and onboarding details are provided directly to approved makers and may change before launch.

Market data loop

  • Discover active markets and retrieve the current book before quoting.
  • Use public WebSocket channels for low-latency book, ticker, and trade updates.
  • Reconcile from REST after reconnecting; realtime frames are notifications, not a durable event log.
  • Respect the published price and quantity increments for each market.
GET/api/markets
GET/api/markets/{ticker}/orderbook
WS/ws

Order hygiene

Keep a heartbeat while quotes are resting, verify their scoring status, and cancel open orders when a strategy pauses or shuts down. Treat a missed heartbeat as a reason to refresh account state before resuming.

POST/api/clob/heartbeats
GET/api/clob/order-scoring
POST/api/clob/orders-scoring
DELETE/api/portfolio/orders

Monitoring

  • Track request errors, rate limits, heartbeat health, and reconnect frequency.
  • Alert when open-order state differs between the strategy and the account API.
  • Pause quoting when market status changes or reference data becomes stale.
  • Use one account per strategy when you need independent limits and operational controls.

Beta expectations

Beta activity uses test Dots with no monetary value. Coordinate with the majjha team before load testing or enabling an unattended strategy, and design clients to tolerate additive fields and documented rate-limit responses.

Need maker access?

Share your intended markets, peak request rate, and whether you need read or trade access during onboarding.