Trades and history

Trades appear in these reads only after their funding is confirmed on chain, so they never expose unfunded breakdowns.

Customer history

Use GET /v1/trades with a customer session to list that customer’s trades. Pages hold 20 trades. Pass the nextCursor from one response as after in the next request.

By default, trades are ordered by when they were funded. With includePending=true, they are ordered by when they were created.

Reconcile from your server

Call GET /v1/trades with your partner secret to recover or reconcile across customers. The credential must permit the integrationId you send. Besides integrationId, the call accepts partnerUserId, status, updatedSince, until, after and limit (1 to 100). Keep the same filters and the same until value on every page of one cursor sequence.

Read one trade

GET /v1/trades/{tradeId} returns the full trade. Two fields need care:

• availableActions lists candidate actions. The real check happens when you prepare an action, so treat it as a hint.
• paymentInstructions appears only after funding is confirmed. On a BUY, it shows the merchant account that the customer pays. On a SELL, it shows the customer’s own receiving account. See Buy walkthrough and Sell walkthrough.

See Trade lifecycle for the statuses.