GET v3/products
GET/v3/products
List your products, with filters and pagination.
Allows the retrieval of multiple products and their related details. This endpoint supports 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 cursor-based pagination.
- See also this article on pagination.
Filters
The GET v3/products endpoint supports filtering on the following attributes: sku and barcode. Each of these is explained below. Filters can be used in combination with each other and with pagination to allow full access to the desired subset of product resources.
Filtering on sku
The endpoint allows setting a filter on the sku of products. The filter accepts multiple sku values, each of which must be URL encoded and separated by a comma. Each sku returns at most one product resource but could also return none. Be aware that the SKUs must be URL encoded to avoid being interpreted incorrectly.
GET {host}/v3/products?filter[sku][in]=ABC,DEFwill return theproductswith skuABCandDEF.GET {host}/v3/products?filter[sku][in]=ABC%2CDEFwill return theproductwith the skuABC,DEF.
Filtering on barcode
The endpoint allows setting a filter on the barcode of products. The filter accepts multiple barcode values, each of which must be URL encoded and separated by a comma. Each barcode returns at most one product resource but could also return none. Be aware that the barcodes must be URL encoded to avoid being interpreted incorrectly.
GET {host}/v3/products?filter[barcode][in]=848017,748222will return theproductswith barcodes848017and748222.GET {host}/v3/products?filter[barcode][in]=848017%2C748222will return theproductwith the barcode848017,748222.
Including related resources
This endpoint does not support inclusion of other resources.
Limitations of GET v3/products
When using this endpoint, expect the following limits on the result set:
- At most 100
productswill be returned regardless of thepage[size]settings provided in the request. - Ordering is based on the
idof theproductin ascending order. - When providing multiple filters they will all be applied (so both
filter[sku][in]andfilter[barcode][in], will result in products having both these values). - Users are rate-limited to 5000 requests per hour on this service.
Request
Responses
- 200
- 401
- 403
- 406
- 415
- 429
A successful response consists of zero or more product resources being returned as part of the data
element in the response body that match the filtering and pagination query parameters provided in the
request. Also, a set of pagination links will be returned to assist with further invocations of the endpoint.
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.