AXS APIaxs.com ↗
Access AXS.com event listings, venue data, performer info, and ticket pricing via 10 endpoints covering US and UK events with category and location filters.
What is the AXS API?
The AXS API exposes 10 endpoints for querying live event data from AXS.com, including ticket pricing, venue coordinates, performer details, and marketplace availability. search_events returns flattened results across events, venues, and performers in a single call, while get_event_detail delivers full structured data for a specific event by ID — covering both AXS US and AXS UK platforms.
curl -X GET 'https://api.parse.bot/scraper/bc13dcb0-0273-4999-8fec-897c0aad9c96/search_events?lat=40.7128&lng=-74.006&page=1&query=concert&results=5&category=Music' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for events, performers, or venues by keyword, category, and location. Returns matching events, venues, and performers in a flattened structure with total counts. Paginates via the page parameter.
| Param | Type | Description |
|---|---|---|
| lat | number | Latitude for location-based search |
| lng | number | Longitude for location-based search |
| page | integer | Page number for results |
| query | string | Search keyword (event title, artist name, or venue name) |
| results | integer | Number of results per page (max 50) |
| category | string | Major category: Music, Sports, or ArtsOrFamily |
{
"type": "object",
"fields": {
"events": "array of event objects with id, eventTitle, venue, performers, ticketingStatusText, etc.",
"venues": "array of venue objects with venueId, venueTitle, address, geo",
"performers": "array of performer objects with performerId, performerTitle, media",
"events_total": "integer, total number of matching events",
"venues_total": "integer, total number of matching venues",
"performers_total": "integer, total number of matching performers"
},
"sample": {
"data": {
"events": [
{
"id": "1422763",
"venue": {
"venueId": 102546,
"venueTitle": "Bass Concert Hall"
},
"eventId": 1422763,
"eventURL": "https://www.axs.com/events/1422763/my-hero-academia-in-concert-tickets",
"eventSlug": "my-hero-academia-in-concert-tickets",
"eventTitle": "My Hero Academia in Concert",
"majorCategory": "ArtsOrFamily",
"ticketingStatusText": "Buy Tickets"
}
],
"venues": [
{
"venueId": 126134,
"venueTitle": "RNCM Concert Hall"
}
],
"performers": [
{
"performerId": 1101901,
"performerTitle": "ABBA The Concert"
}
],
"events_total": 2504,
"venues_total": 57,
"performers_total": 246
},
"status": "success"
}
}About the AXS API
Event Search and Discovery
search_events accepts a free-text query, a category (Music, Sports, or ArtsOrFamily), and optional lat/lng coordinates. Each response includes three parallel arrays — events, venues, and performers — plus integer totals for each. Pagination is handled via the page parameter with up to 50 results per page. For category-scoped browsing without a keyword, get_events_by_category and get_featured_events return arrays of event objects that include startDatetime, venueTitleLocalized, and veritix-sourced pricing fields.
Pricing and Availability Fields
Several endpoints explicitly extract minPrice and maxPrice from veritix pricing data and attach them directly to each event object. search_events_by_category_with_pricing adds these fields to category results, while search_events_by_category_with_pricing_daterange further filters those results by start_date and end_date (ISO format YYYY-MM-DD). When pricing data is absent for an event, both price fields return null rather than omitting them. search_axs_ticketed_events_by_category narrows results further to only events where axsTicketed is true, which excludes third-party-listed events.
Marketplace and UK Platform Coverage
get_marketplace_events returns only events available on the AXS secondary resale marketplace, identified by an axsMarketplace flag on each result. For UK coverage, get_uk_events_by_category queries the AXS UK platform (tickets-uk.axs.com) scoped to UK geography and returns a uk_url field alongside standard pricing and performer fields. get_event_detail handles both US and UK event IDs — the url field in the response points to the correct regional domain based on the event.
Venue and Location Data
list_cities returns paginated city records with geo (latitude/longitude), countryCode, stateNameLocalized, and countryNameLocalized. When lat/lng are supplied, results are sorted by distance. Venue objects across all search endpoints include venueId, venueTitle, address, and geo coordinates, making it straightforward to cross-reference events with specific locations.
The AXS API is a managed, monitored endpoint for axs.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when axs.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official axs.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a local event calendar by querying
get_featured_eventswith lat/lng and displayingstartDatetimeandvenueTitleLocalized. - Track ticket price ranges for upcoming concerts using
search_events_by_category_with_pricingwith category=Music and readingminPrice/maxPrice. - Find resale-available events near a location using
get_marketplace_eventsand filtering on theaxsMarketplaceflag. - Monitor UK live events by category using
get_uk_events_by_categoryand extractinguk_urland pricing fields. - Filter events within a specific travel window using
search_events_by_category_with_pricing_daterangewithstart_dateandend_dateparameters. - Aggregate performer metadata across search results by collecting
performerTitleandmediafields from theperformersarray. - Build a venue directory from the
venuesarray returned by search endpoints, usingvenueId,address, andgeofor mapping.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does AXS have an official public developer API?+
What does `get_event_detail` return that the search endpoints don't?+
get_event_detail returns a full details object for a single event, including relatedMedia, complete dates data, and the full performers array with more granular fields. Search endpoints return flattened summaries suitable for listing pages; get_event_detail is suited for building individual event pages where you need the complete record.Does the API cover individual seat maps or row-level inventory?+
How does pagination work across the search endpoints?+
page integer parameter and a results parameter capped at 50. The response includes events_total, venues_total, and performers_total counts so you can calculate how many pages to fetch. Endpoints like search_events_by_category_with_pricing_daterange apply date filtering after fetching a page, so the returned events_total reflects only matches on that page, not a global filtered count.