Retrieve and update individual transactions, bulk update multiple transactions, and manage transaction statuses via the Corsa API.
This guide covers managing transactions after ingestion — retrieving individual transactions, updating transaction data, updating statuses, and applying bulk updates across multiple transactions.Full API endpoint details are available in the API Reference (requires API credentials).
To ingest new transactions (deposits, withdrawals, trades, transfers), see the Ingest Operations guide.
Endpoint:PUT /v1/transactions/{id}Update mutable fields on an existing transaction. Useful for enriching transactions with data that arrives after initial ingestion (for example, a blockchain hash that’s confirmed later, or updated risk data from a screening provider).
PUT /v1/transactions/txn-uuid-123Content-Type: application/json{ "txHash": "0xabcdef1234567890...", "paymentRail": "ACH", "transferType": "DOMESTIC", "customFields": { "internalNotes": "Confirmed by compliance team" }}
Endpoint:PATCH /v1/transactions/bulk/updateApply the same field changes to up to 100 transactions in a single request. Use this to enrich or correct a batch of transactions efficiently.
Endpoint:POST /v1/transactions/lookup-by-hashBatch-lookup transactions by their on-chain transaction hash. Useful when a blockchain analytics provider or internal process identifies a hash and you need to find the corresponding Corsa transaction records.
POST /v1/transactions/lookup-by-hashContent-Type: application/json{ "txHashes": [ "0xabc123def456...", "0x789xyz..." ]}
Array of blockchain transaction hashes to look up. Maximum 100 per request.
The response returns an array of matching transaction objects for each hash provided. Hashes that do not match any stored transaction are omitted from the response.