Feed

get/api/feed/v1/events/{eventId}/sections/live

Request

  • Base URL: https://api.findticker.com
  • URL: https://api.findticker.com/api/feed/v1/events/{eventId}/sections/live
  • Auth: HTTP bearer

Path parameters

eventIdstring required

Response

Seats open for sale RIGHT NOW in each section of one event, with the section's total capacity, the share of it no longer open, and the lowest, median and highest price of the open seats. Keyed by the section's ticket code. This is the live state of the house: GET /v1/events/{eventId}/sections is the per-section history. capacity and percent_taken are null, never 0, for an event whose seat map states no capacity. percent_taken is capacity minus the open seats: a seat a buyer took, one held back and one withdrawn all count the same, so it is never a count of sales. meta.covered false means the event has no live seat reading at all. sold_or_pulled says how many listings and tickets left the resale market in the last 24 hours and 7 days and what they were last asking, weighted by tickets: a listing leaves the market because a buyer took it or because its seller withdrew it, and nothing here tells those apart, so it is not a count of sales and the average is an asking price, not a clearing price. It is null, never 0, for an event whose resale listings we do not hold at listing level, which is most events. The top level sold_or_pulled splits the event total by source, never summed into one figure, and its sections list is complete where the sections array above is only the sections with a seat still open. Every key holder is entitled to this reading. Costs ONE UNIT whatever the section count.

event_idstring nullable required
seat_map_versionstring nullable required

The version of the seat layout these counts were read under. Null when the event has no live seat reading.

as_ofstring nullable required

When these counts were last seen, UTC.

Example response

{
  "sold_or_pulled": {
    "window_days": 7,
    "sections": [
      {
        "section": "109"
      }
    ]
  },
  "sections": [
    {
      "section": "109",
      "base_section": "109"
    }
  ],
  "meta": {
    "units_charged": 1
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.