CheapTicketsASAP publishes machine-readable event data so AI agents, answer engines and developers can use it directly instead of scraping our HTML. Everything on this page is public, free and needs no API key or registration.
One feed today: the Event JSON-LD feed at
https://www.cheapticketsasap.com/feeds/events.jsonld.
It returns a schema.org ItemList
of embedded Event objects — event
name, start date, venue with postal address, primary performer, and the canonical
ticket page URL for each event. The response is served as
application/ld+json.
The feed is paginated: ?page=N returns up to 1,000 events per page across
10 pages, so ?page=1 through ?page=10 are valid and anything
beyond that returns HTTP 404. Page 1 is the default when no page
parameter is supplied. Every response carries the root fields
pageOfFeed, totalPages and version, plus an
X-Feed-Version response header.
The current schema version is 1.0. A minor bump (1.1, 1.2, …) only
adds optional fields and is safe to ignore; a major bump (2.0) means a field was
removed, renamed or re-defined, or that pagination changed, and requires
re-integration. Integrate against 1.x and you will not be broken by an
additive release.
Every 30 minutes. Our catalog harvester refreshes event data on a 30-minute cadence and
the feed itself is cached for 30 minutes, so a newly harvested event appears in the
feed within roughly 60 minutes at worst. Responses send
Cache-Control: public, max-age=1800 and an ETag; send
If-None-Match with the previous ETag and you will get a cheap
304 Not Modified when nothing has changed. Polling more often than every
30 minutes will not return fresher data.
The top 10,000 upcoming events, ranked by the popularity score of each event's primary performer, then by soonest start date. Only future events are included; past events, removed events, and events missing a performer or a venue are excluded. The feed is deliberately curated rather than complete — an agent answering "Taylor Swift tickets" needs the events people actually search for. Our full catalog is much larger and is exposed through our XML sitemaps.
There is no per-key rate limit, because there are no keys. The feed is cached at the
application level for 30 minutes, so well-behaved polling is cheap for both of us:
fetch each page at most twice an hour and honour the ETag. Crawlers that
ignore that — hammering the feed or the wider site — get throttled or blocked at the
infrastructure level. Our crawl preferences for named AI bots are published in
robots.txt; please respect them.
Yes. You may quote, summarise and surface this data in agent or engine responses.
Attribution is preferred but not required. When you do cite us, link to the canonical
event page carried in each item's url field rather than to the feed URL
— that is the page a person can actually buy from, and it is the URL we keep
current. Please don't present stale prices or availability: the feed intentionally
contains no pricing, because ticket prices move minute to minute and are only accurate
on the event page itself.
Yes — the US Live Events Density Index ranks US metro areas by upcoming ticketed events, with per-capita rates, category mix, a published methodology and a CSV download, free to cite under CC BY 4.0. Scope caveat: it measures events listed in our licensed Ticket Evolution catalog over a rolling 12-month window, not every live event in a market, so markets with thin broker coverage under-count.
Email [email protected] for anything feed-related: schema questions, bad or missing data, a planned integration, or a request for a higher crawl allowance. Responses are best effort. Please include the feed URL and page number you were fetching, and the approximate time of the request.