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
  • execution-service
The contracts and risk engine behind those services live in:
  • execution-contracts
  • risk-core

​
Orderbook flow

1

Discover the market

Read GET /v1/markets to find the canonical market symbol, asset_address, sub_id, and settlement metadata for instruments like USDCcNGN-SPOT.
2

Read the book

Read GET /v1/book and GET /v1/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 /v1/orders, then track fills with GET /v1/orders/{order_id} or the authenticated orders WebSocket channel.
4

Execute matched trades

Let the matcher send crossed-order payloads to POST /execute on execution-service.