Search

Returns the transaction history of one terminal, sorted by date descending and paginated. Use it to reconcile the terminal against your own records, or to recover a transaction_reference you failed to store.

Beta — Early Access

Kushki ONE Cloud is currently in Beta for Perú 🇵🇪. Do not deploy to production without coordinating with the Kushki integration team.

Operation

Operation	Endpoint
Transaction Search	`POST /sync/transaction_search`

Cloud mode exposes a single unified search. For offline local-terminal search, use the Local mode transaction_search_local endpoint.

Request

Only page and size are required. filters and every property inside it are optional — combine just the ones you need.

{
  "page": 1,
  "size": 10,
  "filters": {
    "last_four_digits": "9130",
    "transaction_type": "charge",
    "start_date": 1785560400000,
    "end_date": 1788238799000
  }
}

Filter	Notes
`bin`	First six digits of the card
`last_four_digits`	Last four digits
`client_transaction_id`	The idempotency key you sent
`transaction_reference`	The reference Kushki returned
`transaction_type`	`charge`, `preAuth`, `capture`, `reAuthorization`, `posTip`, `void`, `refund`
`start_date` / `end_date`	Unix timestamps in milliseconds. Send `0` in both to disable date filtering

INFO

transaction_type uses camelCase (preAuth, reAuthorization, posTip) even though the endpoint paths use snake_case. size caps at 500.

Dates are the easy thing to get wrong

start_date and end_date are 13-digit millisecond timestamps. A 10-digit value in seconds is a thousand times smaller, so it lands in January 1970:

What you sent	Symptom
Both fields in seconds	Empty result set
Only `start_date` in seconds	Returns your full history, not the range you asked for
Only `end_date` in seconds	Validation error `2021`, `start_date must be before end_date`

DANGER

The middle case is the dangerous one — the request succeeds and returns data, just far more than you meant. Check the digit count before you reconcile.

The value is an absolute instant on the epoch, with no timezone of its own. Peru does not observe daylight saving time, so America/Lima stays on UTC-5 all year — resolve it with a timezone library anyway:

Got a suggestion on this documentation? Contact us.

Operation#

Request#

Dates are the easy thing to get wrong#

Operation

Request

Dates are the easy thing to get wrong