Transaction Search — Local - Kushki Developer Portal

Queries transaction history stored locally on the terminal.
Does not require internet connectivity — useful for offline reconciliation
or when the acquirer backend is temporarily unreachable.
Results are sorted by date descending.

🚧 Beta — Early Access
This API is in early access. Endpoints, parameters, and response structures
may change without prior notice. Do not deploy to production without
coordinating with the Kushki integration team.

Local search does not support filtering by transaction_type, and only returns what that
specific terminal stored. Use Transaction Search — Online
when you need to filter by operation type or to see the merchant's full history.

Date filtering

start_date and end_date are Unix timestamps in milliseconds (13 digits).

A 10-digit value in seconds is a thousand times smaller than intended, so it lands in January
1970. The symptom depends on which field you got wrong:

What you sent	Resulting range	Symptom
Both fields in seconds	Entirely within January 1970	Empty result set
Only `start_date` in seconds	January 1970 → your end date	Returns the full history, not the range you meant
Only `end_date` in seconds	Your start date → January 1970	Validation error `2021`, `start_date must be before end_date`

The second case is the dangerous one: the request succeeds and returns data, just far more than
you asked for. Check the digit count before you reconcile.

Both fields are optional. Send 0 in both to disable date filtering and page through the full
history.

The value is an absolute instant on the Unix epoch, so it has no timezone of its own. To search a
local calendar day, convert that day's local boundaries in America/Mexico_City to epoch
milliseconds:

Local date and time	UTC offset	Value to send
2026-08-01 00:00:00	UTC-6	`1785564000000`
2026-08-31 23:59:59	UTC-6	`1788242399000`

Mexico stopped observing daylight saving time in October 2022, so most of the country stays on
UTC-6 all year. Resolve America/Mexico_City anyway: the northern border municipalities that
follow US daylight saving are the exception.

Required vs optional. Only page and size are required. The filters object and every
property inside it are optional.

curl --location '/terminal/v1/sync/transaction_search_local' \ --header 'Authorization: nRvpFJZHjqLU4k8Rz2YiDvxA3mQs9oB1cW7eT0=' \ --header 'timestamp: 1700000000000' \ --header 'Content-Type: application/json' \ --data '{ "page": 1, "size": 10, "filters": { "last_four_digits": "9130", "status": "APPROVAL", "start_date": 1785564000000, "end_date": 1788242399000 } }'

Transaction Search — Local

🚧 Beta — Early Access

Date filtering

Request

Responses

Transaction Search — Local

🚧 Beta — Early Access#

Date filtering#

Request

Responses

🚧 Beta — Early Access

Date filtering