Skip to main content
Market data routes help you discover supported pairs, show current prices, inspect order book depth, and reconcile execution activity. They are designed for backend trading automation and internal tools that need deterministic product metadata before placing orders.

​
Market Discovery

Call GET /partner/exchange/markets during startup and refresh it periodically. Use the returned values as the source of truth for:
  • supported pair_id values
  • accepted order types
  • amount and price precision
  • minimum and maximum order sizes
  • trading status
Do not submit an order for a pair that is missing, disabled, or outside the returned limits. The currently supported exchange pair is USD/NGN. Future pairs should be discovered from this endpoint when they become available.

​
Pricing Before Order Submission

Use ticker data for lightweight quote displays. Use order book snapshots before sending a large or price sensitive order, because the top-of-book price alone does not show how much size is available.

​
Historical Reads

Candles and trades are useful for charts, execution review, and detecting unexpected price movement. Always page through historical data using the documented query parameters instead of requesting a large range in one call.

​
Operational Guidance

​
Required Headers

Market data endpoints require X-Api-Key enabled for exchange reads. Common failures include unsupported pair_id, invalid time windows, malformed intervals, or requesting too many records in one call.