Skip to main content
Everything below runs against production. Replace $EVENTORY_API_KEY with your key or export it in your shell first. The Node.js snippets use top-level await, so run them as ES modules (save them as .mjs).
1

Check your key and credits

GET /usage is free and works for every valid key, so it is the safest first call.
A 401 here means the key was not sent or is wrong. If you used a shell variable, check it is actually set: an empty variable sends the request with no key at all.
2

Find the platform key and event id

This step and the next call Live Availability, which is enabled per account on request. Without it, they return 403 forbidden.Live Availability needs a platform key and the event’s id on that platform. GET /events/platforms lists every platform with the regions it accepts and an example id. Cache the result, it costs 5 credits like every call on this API.
The id is normally in the event URL. For Ticketmaster it is the 16-character string at the end of …/event/0200642CF18CAA24; several other platforms take the full event URL instead. See Supported platforms.
3

Pull live availability

A scrape runs synchronously and can take up to 60 seconds. Give your client a 65-second timeout.
sections_type tells you how to read sections; check it on every response. Ticketmaster, AXS, SeatGeek, StubHub, viagogo and VividSeats usually return a seat map, the other platforms flat ticket tiers. See Section types.
4

Watch the event instead of polling

If you want to be told when something changes rather than asking, add the event to your watchlist. Watchlist calls are free.
The response carries the created item under item. Keep its id to update or delete it later. If your key is granted the Notifications API, open the socket; it picks up watchlist changes within 60 seconds. Access to the Notifications API is not part of any API plan and is granted separately to a limited number of partners. See Connecting.website accepts far more platforms than Live Availability does, and an unknown value is rejected with 400. Check it against Watchlist platforms.
5

Look at the history

Market Data answers “how has this been selling?” rather than “what is on sale now?”. One credit per call.
Each hit carries the identifiers you need for the detail endpoints: viagogo_event_id for GET /eventory/data/viagogo/E-{viagogo_event_id} (daily statistics and a price histogram) and ticketmaster_event_id for GET /eventory/data/ticketmaster/{tm_event_id}.

Next

Credits & access

What each call costs and how to tell which APIs your key can use.

Errors

Every error code, what it actually means, and what to do about it.
Last modified on October 31, 2026