List Product Availability Dates
GET/api/products/availability-dates
Availability dates for up to 250 products at once, named by product_ids[] and/or skus[] (unknown ones are left out). Each item has the same shape as Get Product Availability Date — the shape to feed a storefront or retail-partner inventory feed with a back-in-stock date per variant.
products:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
How it is computed: supply is a FIFO queue — free stock on hand today (all warehouses), then the unallocated remainder of every open purchase order line in ETA order. A line's ETA is the earliest open inbound shipment's expected_arrival_date, else the PO's estimated_delivery_date (Available ETA); lines with no ETA queue last. Units already promised to backorders are netted out first. The date is the ETA of the supply that reaches quantity; a late PO never yields a date in the past.
Bundles have no stock of their own: the date is the latest of their components' dates for quantity × quantity_per_unit each, and bottleneck_product_id / bottleneck_sku name the component that decides it. Kits use pre-built stock and their own POs first, then the better of that and building the shortfall from components.
status: in_stock (free stock covers it today), inbound (open POs with ETAs cover it), eta_unknown (covered only with a PO that has no ETA — availability_date is null), no_supply (stock + open POs cannot cover it — null date), not_stocked (a matrix parent, or a bundle with no components).
availability_date is a date-only value (YYYY-MM-DD, account timezone). sources lists the supply consumed to reach the quantity; components holds the same object per component. Read-only: nothing is allocated.
To improve the dates, keep PO and inbound-shipment ETAs current — see Update Purchase Order and Update Inbound Shipment.
Authentication: Requires Bearer token (scope products:read, permission products.index).
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.