GET v3/orders
GET/v3/orders
List your orders, with filters and pagination.
Returns all orders placed.
Pagination
The endpoint supports pagination to split the large collection of resources into smaller, more manageable chunks or pages. This helps to reduce the response size and to improve performance. The endpoint supports only cursor-based technique for pagination.
- See also this article on pagination.
Filters
The GET v3/orders endpoint supports filtering on the following attributes: orderedOn, externalOrderNumber, reference. Each of these are explained below. Filters can be used in combination with each other and with pagination to allow full access to the desired subset of orders.
Filtering on orderedOn
The results returned by this service can be filtered based on the order date of the order. To do so make use of the filter[orderedOn] parameter in the following manner:
GET {host}/v3/orders?filter[orderedOn][lt]={date}will returnorderthat have been ordered before the provided date. Orders that have been ordered on that date are not included in the results.GET {host}/v3/orders?filter[orderedOn][gt]={date}will returnorderthat have been ordered after the provided date. Orders that have been ordered on that date are not included in the results.GET {host}/v3/orders?filter[orderedOn][gt]={date_1}&filter[orderedOn][lt]={date_2}will returnordersthat have ordered between dates {date_1} and {date_1}. Orders that has been ordered on either date are not included in the results.
Filtering on externalOrderNumber
In order to find orders that have a specific externalOrderNumber it is possible to specify one or more values to search for. Be aware that each entry in the list must be URL-encoded in order to be accepted. This means that the characters !\"#$%&'()*+,\:;=?@[] and white-spaces must be percent-encoded (see also the example below). Make use of the filter[externalOrderNumber][in] filter as follows:
GET {host}\v3\orders?filter[externalOrderNumber][in]=%23UK-1003,NL123%2F433will return allordersthat have either#UK-1003orNL123\433asexternalOrderNumber.
Filtering on reference
In order to find orders that have a specific reference it is possible to specify one or more values to search for. Be aware that each entry in the list must be URL-encoded in order to be accepted. This means that the characters !\"#$%&'()*+,\:;=?@[] and white-spaces must be percent-encoded (see also the example below). Make use of the filter[reference][in] filter as follows:
GET{host}\v3\orders?filter[reference][in]=%23UK-1003,NL123%2F433will return allordersthat have either#UK-1003orNL123\433asreference.
Including related resources
The endpoint also supports -to some
degree- the inclusion of information of related resources. The resources that
can be included in the response are limited to the orderItems, the deliveryAddress,
the billingAddress and the pickUpPoint. To get the details of related
entities the include parameter must be added to the URI in the following
way:
GET {host}/v3/orders?include=orderItemswill return for eachorderthe list oforderItemswith their details.GET {host}/v3/orders?include=deliveryAddress,billingAddress,pickUpPointwill return all three types of addresses of eachorderif applicable. Note that thedeliveryAddressandbillingAddressare both of typeaddresswhereas thepickUpPointis of typepickUpPoint.
Limitations of the GET v3/orders
- Users are rate-limited to 1000 requests per hour on this service.
Request
Responses
- 200
- 401
- 403
- 406
- 415
- 429
OK
401 Unauthorized
A 401 Unauthorized response occurs when attempting to access a resource or perform an action that requires authentication, but no valid credentials have been provided. It indicates that the requester is unauthorized to access the requested resource.
The following are common scenarios that may lead to a 401 Unauthorized response:
- Attempting to access a protected API endpoint without providing authentication credentials.
- Providing an invalid or expired authentication token.
- Providing valid authentication credentials, but lacking sufficient privileges to access the requested resource.
- Providing authentication credentials that are valid for a different resource or API endpoint than the one being requested.
403 Forbidden
The HTTP 403 Forbidden client error response status code indicates that the server understood the request but refused to process it. This status is similar to 401 Unauthorized, except that for 403 Forbidden responses, authenticating or re-authenticating makes no difference. The request failure is tied to application logic, such as insufficient permissions to a resource or action.
406 Not Acceptable
A 406 Not Acceptable response occurs when the server cannot provide a response that matches the client's requested format or content language for the requested resource. For instance, if a client sends an Accept header of text/html to an API endpoint that only supports application/json responses, the server would respond with a 406 Not Acceptable status code. This type of response is a required response for JSON:API compatible endpoints.
415 Unsupported Media Type
A 415 Unsupported Media Type response occurs when the server cannot process the request because the media type specified in the request is not supported for the requested resource. For example, if a client sends a request with a Content-Type header of application/pdf to an API endpoint that only supports application/json (the only valid media type for JSON:API), the server would respond with a 415 Unsupported Media Type status code. This type of error-response is a required for JSON:API compatible endpoints.
429 Too Many Requests
The request could not be completed because of a rate limit violation.