The calling party's settled trades (either role)
Authorization
ApiKeyAuth In: header
Query Parameters
Newest-N window — no cursor pagination
1 <= value <= 500100Response Body
application/json
application/json
curl -X GET "https://example.com/trades"[ { "tradeId": "string", "taker": "string", "maker": "string", "direction": "SELL", "qty": "string", "base": "cbtc", "quote": "usdcx", "price": "string", "fee": "string", "settledAt": "string", "status": "settled", "ledger": { "updateId": "string", "receiptCids": [ "string" ] } }]{ "error": "string", "code": "INSUFFICIENT_FUNDS"}The taker's RFQs that closed without a settled trade GET
Expired and cancelled RFQs plus failed settlements — the outcomes that are not trades. The settled blotter is `GET /trades`; rows here never overlap with it. Caller-scoped: no `taker` field in the rows.
Submit the signature for a pending action POST
Two forms. Singular: `{actionId, signature}`. Batch: `{signatures: [{actionId, signature}, …]}` (max 50) — sign everything a call handed you in ONE request. Action ids come from the call that needed them (quote, registration, wallet accept) or from `GET /tx/pending`. `signature` is the base64 Ed25519 signature over the RAW bytes of that action's `hash`. Successful execution advances whatever flow the action belongs to (e.g. a signed quote proposal becomes visible to the taker); the action then disappears from `/tx/pending`.