Skip to main content

Welcome

Numo’s orderbook stack is split across a public orderbook service and a separate match executor. Use this reference for:
  • discovering enabled markets
  • reading the current book and recent trades over REST
  • streaming real-time book, trades, and order updates over the WebSocket
  • submitting signed orders to the matcher
  • checking the status of a submitted order
  • understanding the executor payload that clears matched orders onchain

OpenAPI specification

View the openapi.json file used to build the API reference.

Services covered here

  • markets-service
Settlement runs behind it on execution-service, an internal service you never call. The contracts and risk engine behind those services live in:
  • execution-contracts
  • risk-core

Orderbook flow

Market makers quote the futures on the onchain book, not on this matcher. An order posted here rests until someone else crosses it. To trade now, take from the onchain book.
1

Discover the market

Read GET /markets to find the canonical market symbol, asset_address, sub_id, and settlement metadata for instruments like cNGN-30NOV26.
2

Read the book

Read GET /book and GET /trades from markets-service, or subscribe to the book and trades WebSocket channels for real-time updates instead of polling.
3

Submit signed orders

Post signed order payloads to POST /orders, then track fills with GET /orders/{order_id} or the authenticated orders WebSocket channel.
4

Let matched orders settle

The venue matches crossed orders and settles them on chain for you. You sign the order and never submit the fill.