Skip to main content

Catalog

Returns your events: what could be sold, as opposed to what is for sale right now. Retail polls this every 15 minutes and stores the results. It is the only endpoint whose data Retail keeps.
A catalog entry is a durable description of a real event, safe to store and show. A listing is a quote with a short life. Keep the two apart: nothing here should say how many tickets are purchasable.

Query Parameters

string
required
Your supplier identifier.
integer
default:"1"
1-based page number.
string
ISO 8601 instant. Return only events changed since then. When absent, Retail is doing a full sweep. If your system has no modified-since filter you may ignore this parameter and return everything.
string
Look up a single event, used when Retail re-reads one that looks stale. Optional to support: if you ignore it and return an ordinary page, Retail keeps only the matching row.

Paging

Paging is required. A real catalog runs to tens of thousands of events, and answering in one response will time out. Size your pages so each answers within 30 seconds.
nextPage: null is the only end-of-catalog signal. An empty events array on a page in the middle is treated as a hiccup, not the end. Retail uses absence from the catalog to flag events for review, so ending early by mistake looks like you dropped every event after that page.

Response

array
required
integer | null
required
The next page number, or null when the catalog is exhausted.