Skip to content

Retrieve KYW history

List saved wallet classifications and retrieve an existing check by ID.

Every completed KYW check is stored as an AML search-history record. Save the fresh response's id or auditLogId; both identify the same saved check. Use history when you need the evidence behind an earlier decision.

List saved checks

curl --get 'https://api-dev.cryptoswift.eu/kyw/history' \
  --header "X-Api-Key: $API_KEY" \
  --data-urlencode 'offset=0' \
  --data-urlencode 'limit=10'

The list response is an object with items and total, not a bare array. It lists the authenticated tenant's latest saved entry for each wallet/blockchain combination, newest first. Retrieve an older saved check directly by its ID. offset defaults to 0 and limit defaults to 10. Advance the offset by your page size to request the next page. These endpoints use offset and limit, unlike the Transactions API's _start and _end controls.

Retrieve one saved check

curl --location 'https://api-dev.cryptoswift.eu/kyw/history/{historyId}' \
  --header "X-Api-Key: $API_KEY"

The endpoint returns 404 if that history record does not exist for the authenticated tenant. History reads return stored evidence and do not perform a fresh wallet check or contact an external provider.

The response is a history record, not the same response shape as a fresh GET /kyw/{blockchain}/{address} request. It contains fields such as id, checkType, objectId, blockchain, createdAt, and saved result data such as matchResultData. Consult the Get KYW history record endpoint (Sandbox) for the full schema.

If your policy requires a current classification, run a new KYW check and store its new ID. A saved historical result should not be presented as a new check.

Next steps