Skip to content

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'

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:

ParameterPurpose
_updatedFrom, _updatedToFilter by last update time, inclusive of either bound.
_from, _toFilter by creation date. Omit these to include recent updates to older records.
_directionSelect INCOMING or OUTGOING.
_statusSelect a transaction status.
qSearch by transaction ID or text. Use at least three characters.
_start, _endSelect up to 100 records; the end index is exclusive.
_sort, _orderChoose 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:

  1. Fetch the latest transactions using updatedAt DESC.
  2. Save results by transaction id, replacing older stored states.
  3. Page back far enough to cover changes since your previous sync. Optionally limit results with _updatedFrom, allowing some overlap.
  4. 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"

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.

Next steps