Skip to main content
Both the real-time stream and POST /events/scrape describe an event’s inventory in a sections object whose shape is announced by sections_type. There are two shapes. Write one parser for each and dispatch on the type. GET /events/platforms tells you which shape each platform returns.

OfferSections

A flat object. Each key is an offer id or name; each value is one ticket tier.

SeatMapSections

A nested object. The top-level keys group offers; inside each group, stock is the aggregate for the group and every other key is a section detail object. stock is the only reserved key.
The two APIs group the same detail objects differently. The stream keys the top level by section id and the inner level by offer id. The Live Availability API keys the top level by offer name (ticket tier) and the inner level by venue section id. In both cases the leaf object has the fields below, and section always names the venue section.

Parsing pattern

Treat both shapes as additive: a new field may appear without notice, and any field can be null on platforms that do not expose it.