List transactions
Retrieve the read-only stock transaction history using GraphQL. Transactions record every stock movement (picks, receipts, transfers, etc.) and cannot be created or modified via the API.
Query Structure
Filter Argument
All filters are passed inside thefilter argument. Each filter field accepts an input object with operators (e.g. eq, ilike, from, to, between):
Available Filters
| Filter | Input Type | Operators | Description |
|---|---|---|---|
subtype | SubtypeTypeInputType | eq, in | Transaction subtype (enum input — e.g. PICK, RCV, TRAN) |
category | StringInputType | eq, ilike, like, in, between | Transaction category |
product_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Product ID |
account_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Stock account ID (stock owner) |
warehouse_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Warehouse ID |
created_at | DatetimeInputType | eq, from, to, between | Creation timestamp |
goods_out_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Related goods out ID |
location_from_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Source location ID |
location_to_id | IdInputType | eq, in, gt, gteq, lt, lteq, filled | Destination location ID |
all field also accepts an optional include_archived: Boolean argument to include archived transactions.
More fields and filters available via GraphQL introspection.Authorizations
OAuth 2.0 authentication. Use the client credentials or authorization code flow to obtain an access token.
The subdomain/tenant name identifying which tenant's data to access. Required for all API requests.
Body
GraphQL query string
"query($filter: TransactionFilterType) { transactions { all(filter: $filter) { edges { node { id subtype category quantity created_at product { id code } account { id code } location_from { id code } location_to { id code } completing_user { id } } } } } }"
Query variables including the filter object
{ "filter": { "subtype": { "eq": "PICK" } } }
