Get trade details
Get trade details.
Credential: Customer session or partner secret
Before you call
- A customer session, or an owning partner server credential without Origin.
Reads one trade that the caller owns. A trade exists only after its escrow funding is confirmed on chain, and its first status is CREATED. Before that, track the breakdown, and do not wait for a PENDING trade. Funding confirmation and trade updates can reach the API later than the chain, so poll the existing trade instead of repeating an action.
On a funded trade in CREATED, PAID or DISPUTED, paymentInstructions holds a fixed snapshot of the fiat recipient: the merchant’s account on a BUY, and the customer’s receiving account on a SELL. It is null before funding and after settlement. Trade history and webhook payloads omit account data, and displayLabel identifies the receiving account.
availableActions lists candidate actions for the caller’s role and the trade’s status. Preparing an action checks the current chain state and the dispute timing. RELEASED and CANCELED are final. Dispute details stay on the trade after the dispute is resolved. reason is null when Sinbad has no unambiguous, verified reason.
Confirm with Sinbad that this endpoint is enabled in your environment.
Errors
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Response
A funded trade first appears as CREATED. PENDING, FUNDING_FAILED and FUNDING_EXPIRED are reserved compatibility values, not currently emitted.
Recipient account label from the funded payment snapshot; null before funding or when unavailable. Retained after settlement.
Confirmed dispute only; null before opening and retained after resolution. Roles are public; no internal identity IDs are exposed.
Selected fiat recipient account in CREATED, PAID, and DISPUTED after confirmed funding. BUY uses the merchant account; SELL uses the customer’s receiving account. Null before funding and after settlement.
Customer view of a SELL trade only. The merchant’s saved payment method the fiat is sent from, snapshotted at checkout, so the customer can verify the incoming payment. Same shape as paymentInstructions; data keys match the saved method. Present only in CREATED, PAID, and DISPUTED after confirmed funding; otherwise null (always null for BUY, merchant views, and trades funded before this field existed).
Returned on partner-server reads only.