Request
- Base URL: https://api.findticker.com
- URL: https://api.findticker.com/api/feed/v1/events/{eventId}/seat-history
- Auth: HTTP bearer
Path parameters
Query parameters
seat (default) reads one seat. section reads every seat of section that changed in the window, event every seat of the event, a page of seats at a time in seat order.
How far back to read. Omit to read the seat's whole history, back to its first change.
meta.next_cursor from the previous page, for older changes. Keep days the same across pages. Each page costs one unit.
Response
With scope section or event: every seat of the section or the event that changed in the window, 100 seats a page in seat order, each with its changes as below (at most 200 rows a seat; a longer seat is truncated and carries its own next_cursor), and meta.next_cursor for the next seats. Costs ONE UNIT a page. Otherwise, what happened to one seat, newest first: when it was first seen, every price it was re-listed at with the price before it, every period it was not for sale and when it was for sale again, and whether it has gone, which is taken or pulled. The log does not say which, so a seat that came back is never called gone. Name the seat by place_index, or by section, row and seat together. Reads the seat's whole history by default, back to its first change; the days parameter narrows it. Most events have no per-seat reading at all: meta.covered says so and the array is empty. A seat with a long history comes in pages, newest page first: meta.next_cursor is set while older changes exist, the pages join end to end, and gone is only ever on the first page. Costs ONE UNIT a page whatever the change count.
Example response
{
"changes": [
{
"times": 1
}
],
"meta": {
"units_charged": 1
}
}Changes
No recorded changes to this operation across all 1 revision of this API.