List accounts
Accounts
List accounts
Retrieve accounts using GraphQL. Supports filtering, sorting, and pagination via relay-style connections.
POST
List accounts
Query Structure
Filter Argument
All filters are passed inside thefilter argument. Each filter field accepts an input object with operators:
Available Filters
| Filter | Input Type | Operators | Description |
|---|---|---|---|
code | StringInputType | eq, ilike, like, in, between | Account code |
name | StringInputType | eq, ilike, like, in, between | Account name |
warehouse_id | IdInputType | eq, gt, gteq, lt, lteq, in, filled | Accounts associated with a warehouse |
is_short_pickable | BooleanInputType | eq | Filter by short pickable setting |
Filter Operators
| Input Type | Operators |
|---|---|
| StringInputType | eq (exact), ilike (case-insensitive partial), like (case-sensitive partial), in (array match), between (range) |
| IntegerInputType | eq, gt, gteq, lt, lteq, between |
| DatetimeInputType | eq, from, to, between |
| BooleanInputType | eq (required) |
| IdInputType | eq, gt, gteq, lt, lteq, in, filled |
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
application/json
GraphQL query string
Example:
"query($filter: AccountFilterType) { accounts { all(filter: $filter) { edges { node { id code name is_short_pickable external_system_reference1 vat_number } } } } }"
Query variables including the filter object
Example:
{ "filter": { "code": { "ilike": "ACME" } } }
