- Print
- DarkLight
Retrieve list of product collections, using a cursor based pagination scheme.
List of IDs to filter results by
Cursor to start the results from
Number of items to return up to in the response
Paginated list of collections
An object that encapsulates the return of multiple Collection objects in a paginated result
The unique identifier for the collection
The title of the collection
The description of the collection
The date and time the collection was created, in ISO 8601 format
The date and time the collection was last updated, in ISO 8601 format
The unique identifier for the product
The title of the product
The description of the product
The URL to the image
The alt text for the image
The price of the product, in the currency of the merchant's account and in minor denomination (e.g. pence, cents, etc.)
The Stock Keeping Unit (SKU) for the product
The date and time the product was created, in ISO 8601 format
The date and time the product was last updated, in ISO 8601 format
Block that allows for the arbitary passing of metadata alongside an entity
Can be any value - string, number, boolean, array or object
Block that allows for the arbitary passing of metadata alongside an entity
Can be any value - string, number, boolean, array or object
Provide information to help with paginating through a set of results
Defines whether more results are available from the endpoint
The number of items within the result
The cursor used to access the current set of results, starting with the same entity within the results to enable stable pagination.
The cursor needed to access the next set of results
Invalid request
Response body, based upon RFC-9457 specification, for 400 error codes
Array contain the reason(s) for why the request being invalid
Short human readable explaination for the violation
JSON string containing a human-readable explanation specific to this occurrence of the problem.
Consumers should not parse this property to extract information, but instead should rely on extension properties.
Invalid authentication token
Response body, based upon RFC-9457 specification, for 401 error codes
Invalid authorization permissions
Response body, based upon RFC-9457 specification, for 403 error codes
Internal server error
Error response body, as defined in RFC-9457. Please refer to the specification for more detail on each of the properties.
Other properties can be provided, Extensions, to provide more detailed information for consumers, such as balance in a credit based error.
HTTP status code generated by the origin server.
This value, if provided, should match the HTTP status code sent by the server. But this disagree on the consumer, due to intermediaries such as proxies and caches.
Short, human-readable summary of the problem type
JSON string containing a human-readable explanation specific to this occurrence of the problem.
Consumers should not parse this property to extract information, but instead should rely on extension properties.
JSON string containing a URI reference that identifies the specific occurrence of the problem.