List goods out orders
Retrieve outbound orders using GraphQL. Supports extensive filtering by reference, status, account, warehouse, carrier, dates, and custom fields.
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 |
|---|---|---|---|
reference | StringInputType | eq, ilike, like, in, between | Order reference |
goods_out_status_code | StringInputType | eq, ilike, like, in, between | Status code (DRAFT, PENDING, PICK, ALLOCATED, COMPLETED) |
account_id | IdInputType | eq, gt, gteq, lt, lteq, in, filled | Filter by account ID |
warehouse_id | IdInputType | eq, gt, gteq, lt, lteq, in, filled | Filter by warehouse ID |
carrier_id | IdInputType | eq, gt, gteq, lt, lteq, in, filled | Filter by carrier ID |
expected_date_of_dispatch | DatetimeInputType | eq, from, to, between | Expected dispatch date |
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
GraphQL query string
"query($filter: GoodsOutsFilterType) { goods_outs { all(filter: $filter) { edges { node { id reference priority expected_date_of_dispatch goods_out_status { code name } account { id code } warehouse { id code } carrier { id code } } } } } }"
Query variables including the filter object
{
"filter": {
"goods_out_status_code": { "eq": "PENDING" }
}
}
