AXS APIaxs.com ↗
Access AXS.com event listings, venue details, performer data, and ticket availability via 5 structured endpoints covering search, categories, and featured events.
What is the AXS API?
The AXS API exposes 5 endpoints covering event search, detailed event records, city listings, featured events, and category browsing from AXS.com. The search_events endpoint returns matched events, venues, and performers in a single response, each with its own paginated results array. Event records include ticketing status, performer media, venue geo-coordinates, and start datetimes — enough to build a full event discovery or ticketing availability tool.
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'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace axs-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""
AXS.com Event Discovery — search events, browse by category, and get event details.
Get your API key from: https://parse.bot/settings
"""
from parse_apis.axs.com_api_scraper import AXS, Category, EventNotFound
client = AXS()
# Search for music events by keyword, limit total items fetched.
for event in client.events.search(query="concert", category=Category.MUSIC, limit=3):
print(event.event_id, event.event_title, event.ticketing_status)
# Browse events by category — single-page result, capped.
for event in client.events.by_category(category=Category.SPORTS, limit=5):
print(event.event_id, event.major_category)
# Drill into a single event for full details.
first = client.events.search(query="concert", limit=1).first()
if first:
detail = client.events.get(event_id=first.event_id)
print(detail.event_title, detail.slug, detail.url)
# Typed error handling for a non-existent event.
try:
client.events.get(event_id="9999999999")
except EventNotFound as exc:
print(f"Event not found: {exc.event_id}")
# List nearby cities sorted by distance from coordinates.
for city in client.cities.list(lat=40.7128, lng=-74.006, limit=3):
print(city.city_name, city.state_code, city.country_code)
print("exercised: events.search / events.by_category / events.get / cities.list / EventNotFound")
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
The search_events endpoint accepts a free-text query alongside optional lat/lng coordinates and a category filter (Music, Sports, or ArtsOrFamily). It returns three parallel result sets: events (with eventTitle, venue, performers, and a unique id), venues (with venueId, venueTitle, address, and geo coordinates), and performers (with performerId, performerTitle, and media). Each set includes a total count and supports pagination via page and results parameters.
Event Detail and Category Browsing
get_event_detail takes a required event_id (numeric string) and an optional slug — the URL slug significantly improves lookup reliability. The response wraps a details object containing eventTitle, venue, performers, ticketingStatusText, relatedMedia, and date fields, along with a full AXS page url and the resolved slug. For broader discovery, get_events_by_category accepts a required category and an optional subcategory string to narrow by genre or sub-type, returning event objects with titleLocalized, venueTitleLocalized, startDatetime, and pricing info sourced from Veritix.
Location Utilities
list_cities returns all AXS-supported cities with cityNameLocalized, stateNameLocalized, countryNameLocalized, geo coordinates, and country/state codes. Passing lat/lng sorts results by distance. get_featured_events surfaces homepage-promoted events for a given location (defaulting to New York if no coordinates are supplied), returning an array with titleLocalized, venueTitleLocalized, startDatetime, media, and Veritix pricing data alongside a numberOfResults count.
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_events_by_categorywith user coordinates and a Music or Sports category filter. - Display real-time ticketing availability by pulling
ticketingStatusTextfromget_event_detailfor specific event IDs. - Populate a venue directory using the
venuesmatches fromsearch_events, including address and geo fields. - Create a performer profile page by extracting
performerTitleandmediafrom theperformersarray in search results. - Show featured events on a geo-aware landing page using
get_featured_eventswith the visitor's lat/lng. - Support city-picker UI components with the full city list and coordinates returned by
list_cities. - Track event availability changes by polling
get_event_detailforticketingStatusTexton a set of monitored event IDs.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does AXS have an official developer API?+
What does `search_events` return for a keyword query, and can I filter by location?+
events, venues, and performers, each with their own matches array and a total count. You can pass lat and lng to bias results geographically, and use category to restrict to Music, Sports, or ArtsOrFamily. Pagination is controlled via page and results parameters.Does the API expose individual ticket seat maps or per-seat pricing breakdowns?+
ticketingStatusText and Veritix pricing info at the event level, but seat-level maps and per-row pricing are not part of any endpoint's response shape. You can fork this API on Parse and revise it to add an endpoint targeting seat-map data if that granularity is needed.How reliable is the `event_id` alone for looking up event details?+
event_id to get_event_detail can occasionally return ambiguous results. The slug parameter (the URL slug from an AXS event page, e.g. taylor-swift-the-eras-tour-tickets) is strongly recommended alongside the ID to ensure the correct event record is returned.Does the API cover events outside the United States?+
list_cities returns cities with countryCode fields indicating international coverage, and search_events with coordinates can return non-US results where AXS operates. However, coverage depth varies by market and is determined by what AXS.com lists in a given region — there is no explicit international-only filter. You can fork the API on Parse and revise it to add region-scoped filtering if your use case is limited to specific countries.