AXS

AXS is a global live event ticketing platform operating across the US, UK, Europe, and international markets for concerts, sports, and festivals. AXS is the official ticketing partner for a large number of major venues and sports franchises, including many NBA, NHL, and Premier League clubs, and operates its own mobile-first ticket delivery system.

MoEngage <> AXS

AXS does not currently offer a public events discovery API for campaign personalisation. Their existing developer tools are scoped to venue operator use cases such as access control and ticket redemption. Two paths are available depending on your preference:

Direct access : contact the AXS partnerships team at solutions.axs.com/us/partnerships-integrations to discuss bespoke API access.
Via TicketsData : connect through TicketsData, a third party aggregator building a unified feed that will include AXS alongside other major platforms. The integration steps below document this path.

Integration

schedule

No public API available

A direct AXS public events discovery API is not currently available for campaign personalisation. The steps below document the TicketsData path, which will be ready to configure once AXS support goes live on their feed. Monitor the TicketsData AXS integration overview for the latest status, or reach out to the AXS partnerships team directly at solutions.axs.com/us/partnerships-integrations.

Step 1: Get your TicketsData credentials

TicketsData is a unified ticketing data API that normalises inventory from multiple major platforms — including Ticketmaster, StubHub, SeatGeek, and others — into a single endpoint. AXS support is listed as coming soon on dedicated plans.

Monitor ticketsdata.com/blog/axs-tickets-api or ticketsdata.com/docs for updates on when AXS is added to the TicketsData feed.
Once available, sign up for a TicketsData account at ticketsdata.com and obtain your API credentials (username and password).
Identify the specific AXS event URLs you want to personalise campaigns around. TicketsData uses the live platform event URL as the key to fetch inventory, for example: https://www.axs.com/events/12345/artist-name-tickets.

Step 2: Set up the Content API on MoEngage

Navigate to Dashboard > Settings > APIs and open the Content API tab.
Click Add Content API.
Fill in the details using the table below as a reference.

Key Value

Name Choose a descriptive name, for example AXS Events via TicketsData. This name will identify the API when you reference it inside campaign templates.

Method GET

API URL

https://ticketsdata.com/fetch

This is the TicketsData unified fetch endpoint. You pass the platform name and an event URL as query parameters and receive normalised ticket inventory in return. Refer to the TicketsData API documentation for the full parameter reference.

Key Value Parameters

Add the following parameters:

Parameter	Example value	Notes
`username`	Your TicketsData email	Your TicketsData account email address. Keep this static.
`password`	Your TicketsData password	Your TicketsData account password. Store securely.
`platform`	`axs`	Specifies AXS as the source platform. Set this as a static value.
`event_url`	`https://www.axs.com/events/...`	The full AXS event page URL for the specific event. This can be a static value per Content API configuration.

Click Validate to confirm the platform returns a response, then click Save. The Content API is now available to reference inside any campaign across all supported channels.

Once saved, refer to the MoEngage documentation on using Content APIs in campaigns to learn how to reference the response fields inside your campaign templates.

Understanding the API response

The TicketsData API wraps the platform's raw response in a standard envelope. The fields most commonly used in campaign templates once AXS data is available are shown below. Exact field names will be confirmed in the TicketsData documentation when AXS support goes live.