List bundles
List the bundles stored for a store. Each product is looked up in your catalog, so you get SKUs and names rather than bare identifiers.
Finding one bundle
Pass parent_sku to return just that bundle. The lookup goes through your
catalog, so a bundle created in the Redo UI is found too. sku_resolved
tells you whether the SKU exists at all, as opposed to existing but having
no bundle. If the SKU is on more than one variant, you get every matching
bundle; use parent.variant_id to tell them apart. Filtered requests are
not paged.
Quantities
Each child carries quantity, the number of units of that product in the
bundle. This mirrors what you send on PUT.
Products that no longer exist
A product can be deleted after a bundle is built. When that happens the
entry has resolved: false and sku and name are null. A resolved
product with a null sku simply has no SKU set; such a bundle can only be
managed from the Bundles page in Redo.
Paging
X-Page-Size sets the page size, up to 250 (default 50). When more bundles
remain, the response includes an X-Page-Next header; send it back as
X-Page-Continue for the next page. Treat the cursor as opaque.
Requires the returns_read scope.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Page marker, from the X-Page-Next header of the previous response
Page size, defaults to 50
1 <= x <= 250Path Parameters
Store ID
"64e5a8a1af49a89df37e4ee7"
Query Parameters
Return only bundles whose parent product has this SKU. Case-sensitive. If the SKU is on more than one variant, every matching bundle is returned.