Endpoints

These are the current developer routes.

How to use this pageKeep this open when you are wiring the flow into a backend. It is a quick map of what exists and which step comes next.

Method	Path	Purpose
`GET`	`/api/developer/catalog`	Returns the current provider list, webhook notes, and quickstart summary.
`POST`	`/api/developer/quotes`	Compares eligible provider routes for a buy or sell request.
`GET`	`/api/developer/provider-bank-list/:provider`	Returns the canonical bank codes and names accepted for a selected provider.
`POST`	`/api/developer/bank-accounts/resolve`	Resolves Nigerian bank details before sell order creation.
`POST`	`/api/developer/orders`	Creates a buy or sell order and returns the routed transaction payload. If an active order window already exists on the same rail, the response can return `PAYCHAIN_ACTIVE_INTENT_CONFLICT`.
`GET`	`/api/developer/orders/intent`	Returns the active payment window for a customer, token, and network.
`POST`	`/api/developer/orders/:transactionId/monitor-status`	Rechecks order status when a callback is delayed or missing.

Why the catalog matters

Use the catalog response to confirm the provider list, request hints, webhook headers, and quickstart notes. For sell orders, resolve the bank account first when you do not already have a confirmed accountName. If you want to show a provider-specific list of accepted bank codes in your UI, call /api/developer/provider-bank-list/:provider first and use the returned bankCode values in order creation.

Reference

Orders

Bank details

Why the catalog matters

​Why the catalog matters

Why the catalog matters