Get ticket availability and schedules for a date range
Returns the dates, timeslots, remaining capacity, and indicative prices for ticket and package products between fromDate and toDate. A package lists the start times every one of its components can honour, priced as the sum of its components (see items). This is availability data with no customer context, so it is cheap to call and safe to cache; use it to build a calendar or date-picker. It does not reserve capacity and the prices shown do not reflect any customer-specific discounts. Note that a single product can have several admissions, each with its own schedule and price. Scope the search with the category and skus query filters; one of the two is required, and skus alone searches every category. An unknown category or SKU is not an error, it just returns no results.
Headers
Identifies which store this request is for. Required on every store-scoped route. It is not authentication and not a secret — it grants no privileges and is safe to send from a browser. You receive the value once your Entria backend has been created and configured. Missing header returns 400; an unknown store returns 404.
Query parameters
Start of the date range to check, in YYYY-MM-DD format. Required, and not after toDate. The range from fromDate to toDate cannot exceed 60 days.
End of the date range to check, in YYYY-MM-DD format. Required, and not before fromDate. The range from fromDate to toDate cannot exceed 60 days.
Medusa category handle to filter by, e.g. tickets or memberships. Matched exactly against the product’s own categories, so a parent handle does not match its children. Omit it to match products in any category — skus must then scope the search. Either this or skus is required.
Comma-separated list of product SKUs to filter by. Either this or category is required.
Whether capacity must be realtime. Defaults to true: capacity-tracked products are read live from Business Central (60s edge cache), so remainingCapacity is current and sold-out slots are omitted. Pass false when the caller needs only times and prices — a “from” price preview, a calendar of opening days — and products answer from the schedule index instead, which is cheaper and cached longer. NOTE what the index cannot say: it stores no capacity count, so such a response carries no remainingCapacity, never reports SOLD_OUT, and still lists slots that are sold out. Do not price or gate a purchase on it. Products without capacity control are unaffected and answer from the index either way.
Response
Dates in the requested range, each with the products available on that date, their timeslots, indicative price, and — for capacity-tracked products when withCapacity is not false — remaining capacity.