GET v3/inboundPackingSlips
GET/v3/inboundPackingSlips
List your inbound packing slips and their status, with filters and pagination.
Allows the retrieval of inboundPackingSlips and their current status. This endpoint support pagination and various filters as indicated below.
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 the cursor-based technique for pagination.
- See also this article on pagination.
Filters
The GET v3/inboundPackingSlips endpoint supports filtering on the following attributes: status, receivedOn and completedOn. 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 inboundPackingSlip resources.
Filtering on status
The end point allows to set a filter on the current status of inboundPackingSlips. For more details on the various statusses see inboundPackingSlipStatus.
GET {host}/v3/inboundPackingSlips?filter[status][in]=EXPECTED,COMPLETEDwill return allinboundPackingSlipsthat have either the statusEXPECTEDorCOMPLETED.
Filtering on receivedOn
To filter inboundPackingSlips for which the inbound has been received before or after a particular date it is possible to specify the filter[receivedOn][lt] and filter[receivedOn][lt]. The received on date represents the date at which the inbound has started.
Filtering on completedOn
To filter inboundPackingSlips for which the inbound has been completely processed and completed before or after a particular date it is possible to specify the filter[completedOn][lt] and filter[completedOn][lt]. The value of the completedOn attribute represents the date at which the inbound was completed and no further items are expected.
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 inboundPackingSlipItems.
To get the details of related entities included in the response make use of the include query-parameter in the following way:
GET {host}/v3/inboundPackingSlips?include=inboundPackingSlipItemswill return for eachinboundPackingSlipthe list ofinboundPackingSlipItemswith their details.
Limitations of GET v3/inboundPackingSlips
When using this endpoint, expect the following limits on the result set
inboundPackingSlipsolder than 90 days are not returned using this method.- At most 100
inboundPackingSlipswill be returned regardless of the page[size] settings provided in the request. - Ordering is based on the id of the
inboundPackingSlipin ascending order. - Users are rate-limited to 120 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.