get_event_ga_history
Event General Admission History
Reads only.
Use this for open ticket counts in general admission sections over time. Use get_event_sections_live instead for what is open now, and get_event_seat_history for one reserved seat. How many tickets each GENERAL ADMISSION section of one event had open over time. General admission sections have quantities, not seats, so get_event_seats_live and get_event_seat_history never show them; this does. Without section, sections summarizes each one: open_count after its newest change, peak_open_count and peak_at, observed_additions and observed_removals, first_observed_at, last_changed_at (null when it never changed after its first observation) and removed_at (when it left the section list). Name a section to add its exact points, oldest first, one per observed change, paged with cursor. The additions and removals are sums of OBSERVED changes: a return or a re-release of the same ticket adds again, and a ticket held for a moment and put back adds each time, so never report them as tickets bought, as distinct tickets, or as how many were ever put on sale, and never treat a section's capacity as a number put on sale. Nothing before coverage_start is known. This history runs 15 to 20 minutes behind get_event_sections_live, which is the read for what is open now; an old last_changed_at says when the count last moved, not that nobody is looking. available false means the event has no live seat data at all; an available event with no sections has no general admission history. History depth is capped by plan like the price charts. It is the primary price source, served on the plans that carry that source; any other caller gets a plan_required error with entitled false and required_tier naming the plan that unlocks it, never available false.
Parameters
| Name | Type | Required | Default | Notes |
|---|---|---|---|---|
event_id | string | yes | The event to read. | |
section | string | A general admission section's code, e.g. "GAFLR3", to add its exact points. | ||
occurrence | integer | 0 | 0 unless the event lists the code twice, as sections shows. section and occurrence together name one section. At least 0. | |
limit | integer | 200 | Points per page. From 1 to 1000. | |
cursor | string | next_cursor from the previous page, for newer points. A page after the first carries the points alone. | ||
width | integer | Instead of pages: the shape of the whole history in one answer, as the first, last, lowest and highest point of each of width equal slices of time from the section's first observation to now. At most four points a slice. Use it for the shape of a busy section, which can hold tens of thousands of changes. From 50 to 2000. |