Search and audit transactions
Get the latest transaction updates, filter results, and inspect audit history.
To get the latest activity, request GET /transactions with _sort=updatedAt and _order=DESC. New transactions and recently updated records appear first, including updates to transactions created earlier.
Get the latest transaction updates
curl --get 'https://api-dev.cryptoswift.eu/transactions' \ --header "X-Api-Key: $API_KEY" \ --data-urlencode '_sort=updatedAt' \ --data-urlencode '_order=DESC' \ --data-urlencode '_start=0' \ --data-urlencode '_end=100'
[
{
"id": "233e3fd4-2ef0-477c-a398-8f993d131a19",
"status": "CONFIRMED",
"statusReasoning": null,
"direction": "INCOMING",
"createdAt": "2026-09-11T09:00:00.000Z",
"updatedAt": "2026-11-12T09:02:00.000Z",
"asset": "ETH",
"amount": 0.059625001,
"amountUsd": 223.41,
"amountEur": 193.64,
"metadata": "deposit-8472",
"blockchainInfo": {
"transactionHash": "0x8129df36bf862c55702ab3991c4cc6d00903dc7af4b6f1afc909c216f07e34bd",
"origin": "0x1234567890abcdef1234567890abcdef12345678",
"destination": "0xabcdef1234567890abcdef1234567890abcdef12",
"destinationType": "CUSTODIAL",
"blockchain": "Ethereum",
"isDestinationConfirmed": true,
"destinationWalletId": 7069
},
"vaspInfo": {
"originatorVaspName": "CryptoXYZ",
"originatorVaspEmail": "support@xyz.domain",
"beneficiaryVaspName": "CryptoXchange",
"beneficiaryVaspEmail": "support@cryptox.domain",
"beneficiaryVaspExtraInfo": null
},
"originator": {
"type": "NATURAL",
"name": "Diana DueDiligence",
"accountNumber": "originator-account-123",
"address": "873 Audit Alley",
"country": "AU",
"nationalIdentificatorType": null,
"nationalIdentificator": null,
"customerNumber": null,
"dateOfBirth": null,
"placeOfBirth": null
},
"beneficiary": {
"type": "NATURAL",
"name": "John Smither",
"accountNumber": "AC-123",
"country": null,
"nationalIdentificatorType": null,
"nationalIdentificator": null
},
"travelRuleMessageSource": "CryptoSwift",
"warnings": [],
"riskScore": {
"originatorRiskScore": 72,
"originatorRiskSeverity": "high",
"beneficiaryRiskScore": 8,
"beneficiaryRiskSeverity": "low"
},
"ruleEngine": {
"decision": "REVIEW",
"ruleEngineId": "6292e827-ce05-4cae-a3c8-43e1fb073e1e",
"ruleId": "7f3db7f7-b5b4-4dd7-8de6-e6c15a6eb9e2",
"ruleName": "Review high-risk incoming originator",
"conditions": {
"all": [
{
"field": "riskSeverity",
"value": "high",
"operator": "EQ"
}
],
"any": []
},
"ruleEngineVersion": 3,
"scope": "INCOMING",
"waitForSeconds": null,
"onTimeoutDecision": null
}
}
]
The example was created in September and updated in November, so it appears among recent activity. updatedAt is read-only.
The response is an array. For the next 100 records, use _start=100 and _end=200. Keep sorting and filters unchanged; continue until a page contains fewer records than requested. X-Total-Count reports the matching count and may be estimated for large result sets.
Search transactions
Add filters when you need a specific subset:
| Parameter | Purpose |
|---|---|
_updatedFrom, _updatedTo | Filter by last update time, inclusive of either bound. |
_from, _to | Filter by creation date. Omit these to include recent updates to older records. |
_direction | Select INCOMING or OUTGOING. |
_status | Select a transaction status. |
q | Search by transaction ID or text. Use at least three characters. |
_start, _end | Select up to 100 records; the end index is exclusive. |
_sort, _order | Choose the sort field and ASC or DESC. The default field is createdAt. |
For recent changes only, add _updatedFrom=2026-11-12T00:00:00.000Z. Use ISO 8601 timestamps with a timezone. Either update bound is optional; _updatedTo must not precede _updatedFrom.
Reconciliation pattern
To keep your records current:
- Fetch the latest transactions using
updatedAt DESC. - Save results by transaction
id, replacing older stored states. - Page back far enough to cover changes since your previous sync. Optionally limit results with
_updatedFrom, allowing some overlap. - Save your checkpoint after processing all relevant pages.
Results are live, so allow duplicates and overlapping polling windows. Avoid restricting recovery to one status: records may have changed status.
Use webhooks for immediate notifications. To check one transaction before acting, retrieve GET /transactions/{id}.
Retrieve a transaction's event history
For an audit trail, call GET /transactions/{id}/events. It returns the newest event first:
curl --location 'https://api-dev.cryptoswift.eu/transactions/233e3fd4-2ef0-477c-a398-8f993d131a19/events' \ --header "X-Api-Key: $API_KEY"
[
{
"id": "57599ba1-ef45-4f64-acf5-acb2b1bf07bf",
"transactionId": "233e3fd4-2ef0-477c-a398-8f993d131a19",
"eventType": "STATUS_UPDATED",
"actorType": "API_KEY",
"createdAt": "2026-11-12T09:02:00.000Z",
"userId": null,
"user": null,
"status": "CONFIRMED",
"statusReasoning": null,
"changedFields": [
"status"
],
"piiChanged": false,
"ruleEngine": {
"decision": "REVIEW",
"ruleEngineId": "6292e827-ce05-4cae-a3c8-43e1fb073e1e",
"ruleId": "7f3db7f7-b5b4-4dd7-8de6-e6c15a6eb9e2",
"ruleName": "Review high-risk incoming originator",
"conditions": {
"all": [
{
"field": "riskSeverity",
"value": "high",
"operator": "EQ"
}
],
"any": []
},
"ruleEngineVersion": 3
}
}
]
Events record who changed what and when, the resulting status, and any Rule Engine snapshot. piiChanged flags changes to protected data without exposing their values. A transaction unavailable to your tenant returns 404.