Skip to main content
GET
List transactions
Returns sales transactions visible to your API key, newest changes last. Pair with List products to assemble a catalog-plus-sales view in your warehouse without going through the in-app CSV export flow.

Authentication

Bearer token. See Authentication.

Query parameters

Date-range and per-product/per-store filters (from_date, to_date, product_id, store_id) are not supported on this endpoint. Unsupported query parameters are ignored rather than rejected, so filter client-side or narrow with updated_since.

Response

Results come back under items, ordered by last-updated then id, with an opaque next_cursor for the following page (null on the last page).
See Conventions for number and timestamp formatting.

Incremental pulls

Transaction rows do not carry updated_at in the response, so track the time of your last successful sync on your side and pass it as updated_since on the next run. Page through each run with next_cursor until it comes back null; the server orders by last-updated then id, so a run started mid-stream stays consistent. This catches late-arriving corrections to existing transactions without re-reading the whole history.

Large windows

Pages up to limit=10000 are served from snapshots and are the fastest way to pull a lot of rows. For very large extractions - a full history reload or a BI backfill - prefer an asynchronous export over deep cursor paging.

Example request