AXS API – Real-Time Ticket Data
Live AXS Ticket Listings, All-In Pricing & Full Inventory
AXS is a primary-first platform that also supports in-platform resale, and it models pricing, fees, and venues differently from every other source. TicketsData aggregates that publicly available information and returns it in the same normalized JSON as the rest of your integration — one API call, structured data back.
A different data model, normalized
AXS sits in an unusual position in the market. It sells primary inventory directly on behalf of venues and artists, and it also hosts official resale within the same ecosystem — so a single event can carry both types of listing side by side, under one set of identifiers.
That structure does not resemble how any other marketplace publishes its data. Fee models, section naming, connection fees, and delivery methods all differ. TicketsData aggregates the publicly available listing information and maps it onto the same schema used across every source we cover, so the code you already wrote reads AXS without a single conditional.
API performance
The AXS API is built on dedicated infrastructure designed for reliability and scale. The system is designed to scale horizontally to any request volume — contact our support team or AI agent to discuss capacity requirements for your use case.
Response times vary with event size — a stadium show with several thousand listings takes longer to assemble than a club date. For volume pricing and horizontal scaling options please contact us or use our AI agent.
What the AXS API returns
Every AXS API response includes a complete real-time snapshot for the requested event — the full price ladder with resolved fees, section definitions, delivery methods, on-sale context, and venue details as published on the AXS platform.
Example response
Below is a real response from the AXS API — Geese on the Getting Killed Again Tour at The Midland Theatre, Kansas City. Eighteen price points across three sections, all-in prices from $179 to $591.59, returned in 46.6 seconds.
The fee model is the part worth reading closely. AXS publishes a face value, a stack of separately-calculated service fee components, and a per-section connection fee with its own rate — so the price a buyer actually pays is not a field you can read directly. We resolve the whole model per price point and return face, fees_total, and all_in already calculated. Trimmed here for readability: two of eighteen price points, with two of six fee components shown on each.
{
"status": 200,
"body": {
"status": "ok",
"harvested_at": 1785954482.17624,
"event": {
"event_id": "1414742",
"title": "Geese",
"supporting": "with support from Easy Star All-Stars",
"tour": "Getting Killed Again Tour",
"age_restriction": "All Ages",
"currency": "USD",
"starts_local": "2026-10-30T20:00:00-05:00",
"starts_utc": "2026-10-31T01:00:00",
"timezone": "America/Chicago",
"venue": {
"venue_id": "124780",
"name": "The Midland Theatre",
"address": "1228 Main Street, Kansas City, MO 64105",
"city": "Kansas City",
"state": "MO",
"country": "US",
"latitude": "39.098866",
"longitude": "-94.58359999999"
}
},
"onsale": {
"flow": "PICK_A_SEAT_2D",
"is_resale_enabled": false,
"is_lottery": false,
"queue_it": true,
"ticket_qty": {
"min": 1,
"max": 4
},
"status": {
"onSaleNow": true,
"offSaleDate": "2026-10-31 01:00:00 +0000"
}
},
"sections": [
{
"label": "302",
"general_admission": false,
"sold_out": false,
"connection_fee": 43.35,
"connection_fee_rate": 0.255
},
{
"label": "402",
"general_admission": false,
"sold_out": false,
"connection_fee": 31.88,
"connection_fee_rate": 0.255
},
{
"label": "General Admission Floor",
"general_admission": true,
"sold_out": false,
"connection_fee": 89.25,
"connection_fee_rate": 0.255
}
],
"price_points": [
{
"section": "402",
"general_admission": false,
"availability": 1,
"pricing": {
"face": 125,
"fees": [
{
"name": "Service Fees",
"calculation": "lookup",
"amount": 4.96
},
{
"name": "Service Fees",
"calculation": "lookup",
"amount": 0.55
},
{
"note": "4 further fee components"
}
],
"fees_total": 22.12,
"tax": 0,
"all_in": 179
}
},
{
"section": "General Admission Floor",
"general_admission": true,
"availability": null,
"pricing": {
"face": 439.25,
"fees": [
{
"name": "Service Fees",
"calculation": "lookup",
"amount": 7.33
},
{
"name": "Service Fees",
"calculation": "lookup",
"amount": 0.8
},
{
"note": "4 further fee components"
}
],
"fees_total": 40.33,
"tax": 0,
"all_in": 591.59
}
}
],
"delivery_methods": [
{
"id": "5154",
"label": "AXS Mobile ID - Free (Transfer Delayed)",
"type": "FlashSeats",
"price": {
"perOrder": 0,
"perItem": 0
}
}
]
},
"response_s": 46.634,
"quota_remaining": 661562
}Shared and dedicated plans
The AXS API is available on both shared and dedicated plans. Data format and structure are identical. Dedicated plans provide higher concurrency, full infrastructure isolation, and horizontal scaling — supporting up to 80 requests per minute on dedicated infrastructure. For enterprise or high-volume requirements, please contact us or use our AI agent to discuss a plan tailored to your needs.
Frequently asked questions
Is this an official AXS API?
No. TicketsData aggregates publicly available AXS listing information and serves it through its own API. TicketsData is an independent service and is not affiliated with or endorsed by AXS.
How is AXS data structured compared to other sources?
Identically, once it reaches you. AXS uses its own listing model, fee structure, and venue identifiers, all of which we normalize into the same JSON schema used across every marketplace we cover — so the same integration reads AXS and any other source without branching.
What data does the AXS API return?
The full price ladder for an event: every price point with its section, general admission flag, availability, face value, itemised service fees, and resolved all-in price. Alongside that you get section-level connection fees, delivery methods, on-sale state including queue and lottery flags, ticket quantity limits, and complete event and venue metadata. AXS is a primary-first platform — it sells tickets directly for venues and artists — and supports in-platform resale where the event has it enabled, which the response reports as is_resale_enabled.
Why does an AXS request take 30–60 seconds?
Each request assembles a complete inventory snapshot for the event rather than a partial page, and AXS events frequently carry several hundred listings with individual fee breakdowns. Larger events take longer. You POST a URL once and receive the finished dataset in a single response.
Can it scale to high request volumes?
Yes. The infrastructure is designed to scale horizontally. Contact info@ticketsdata.com to discuss dedicated capacity for your use case.
Do you provide historical AXS data?
No. TicketsData provides real-time marketplace data only.