Ticketmaster provides APIs for event discovery, inventory management, and ticketing solutions.
Ticketmaster provides APIs for event discovery, inventory management, and ticketing solutions. On Nagent, Ticketmaster is exposed as a fully-configurable event management integration that any agent can call — 15 actions, and API_KEY, OAUTH2 authentication. No code is required to wire Ticketmaster into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Ticketmaster to automate the kinds of tasks event management teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Ticketmaster into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Ticketmaster, with input parameters and output schema. Drop these into any step of an agent built in Helix.
TICKETMASTER_EXECUTE_SEASON_TICKETING_COMMANDTool to execute Season Ticketing API commands for ticket management operations. Use when you need to interact with Ticketmaster's Archtics Season Ticketing system for administrative tasks, account management, or event discovery. Supports commands: ping (test connectivity), customer_query (get account info), seats_sold (retrieve sold seat details), event_search (search events), event_details (get event attributes), get_attendance (retrieve attendance data). Note: API may return 202 ACCEPTED for asynchronous operations - caller must poll with provided cookies until receiving 200 OK response.
Input parameters
Header containing version, source system type, system name, and Archtics version
Command details including cmd type, user id, dsn, and optional additional parameters
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_ATTRACTION_DETAILS2Tool to retrieve detailed information about a specific attraction by ID from Ticketmaster Discovery API v2. Use when you need attraction details with optional licensed content filtering.
Input parameters
ID of the attraction
The locale in ISO code format. Multiple comma-separated values can be provided. When omitting the country part of the code (e.g. only 'en' or 'fr') then the first matching locale is used. When using a '*' it matches all locales. '*' can only be used at the end (e.g. 'en-us,en,*')
True if you want to display licensed content
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_ATTRACTIONSTool to retrieve a list of attractions. Use when you need to search for artists, teams, or performers by various criteria such as keyword, classification, or country.
Input parameters
Page number (zero-based).
Number of results per page (1–200).
Sorting of results. Common values: 'name,asc', 'name,desc'.
Entity type filter (e.g., event, venue, attraction).
Content source. One of: ticketmaster, universe, frontgate.
Genre identifier.
Search term to find attractions by name, genre, etc.
Segment identifier.
Subgenre identifier.
2-letter country code (ISO 3166-1 alpha-2).
If true, include test attractions in the response.
Specific Ticketmaster attraction ID to retrieve one attraction.
Sub-segment identifier.
Filter by classification name (e.g., music, sports).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_CLASSIFICATION_DETAILSTool to retrieve detailed information about a specific classification. Use after obtaining a classification ID.
Input parameters
ID of the classification (segment, genre, subgenre, type, or subtype) to retrieve detailed information about
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_CLASSIFICATIONSRetrieves event classifications from Ticketmaster's Discovery API. Classifications provide a hierarchical taxonomy for categorizing events: - Segment: Top-level category (Music, Sports, Arts & Theater, Family, Film, Miscellaneous) - Genre: Secondary category within a segment (e.g., Rock, Baseball, Comedy) - Subgenre: Tertiary category for specific classification (e.g., Alternative Rock, MLB) Use this tool to discover available categories before searching for events, or to understand how events are organized in the Ticketmaster system. The classifications can be filtered by locale, country, or specific classification ID.
Input parameters
The locale in ISO code format (e.g., 'en-us' for US English, 'es-mx' for Mexican Spanish). Controls the language of classification names returned.
Filter classifications by ISO 3166-1 alpha-2 country code (e.g., 'US' for United States, 'CA' for Canada). Returns classifications relevant to the specified country.
Filter to retrieve a specific classification by its unique ID. Use this to get details about a particular segment, genre, or subgenre.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_EVENT_DETAILSTool to retrieve detailed information about a specific event by ID. Use when you have an event's unique identifier and need its full details.
Input parameters
Unique identifier of the event to retrieve details for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_EVENT_IMAGESTool to retrieve images for a specific event by ID. Use when you need to fetch image URLs and metadata for an event.
Input parameters
ID of the event to retrieve images for
The locale in ISO code format. Multiple comma-separated values can be provided. When omitting the country part of the code (e.g. only 'en' or 'fr') then the first matching locale is used. When using a '*' it matches all locales. '*' can only be used at the end (e.g. 'en-us,en,*')
Whether to include licensed content in the response.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_EVENTSSearch for events on Ticketmaster using various filters including location, date range, keywords, classifications, and more. This action queries the Ticketmaster Discovery API to find events matching your criteria. Results are paginated and can be sorted. Use this when you need to: search for concerts/shows/games, find events in a specific location, filter by date range, or discover events by artist/venue. Key capabilities: - Location search: by city, state, postal code, lat/long, or radius - Time filtering: events within date ranges or on-sale dates - Classification: filter by segment (Music/Sports/Arts), genre, subgenre - Keyword search: find events by name or description - Venue/Attraction: get events at specific venues or by specific artists/teams Note: Deep paging limit - size * page must be < 1000. Maximum 200 results per page.
Input parameters
Filter by specific event ID
Filter by city name (e.g., 'Los Angeles', 'New York')
Page number (0-indexed). Default: 0. Note: size * page must be < 1000 due to deep paging limits
Number of results per page (1-200). Default: 20. Note: size * page must be < 1000 due to deep paging limits
Sort order for results. Format: 'field,direction' (e.g., 'date,asc', 'name,desc', 'relevance,desc'). Default: 'relevance,desc'
Unit of measurement for radius search
Filter by DMA (Designated Market Area) ID(s). Comma-separated for multiple
Locale for localized content in ISO format (e.g., 'en-us'). Comma-separated for multiple. Default: 'en'
Radius of search area around latlong or postalCode (use with 'unit' parameter)
Filter by source name (e.g., 'ticketmaster', 'universe', 'frontgate', 'tmr')
Filter by event type ID(s). Comma-separated for multiple
Filter by genre ID(s). Comma-separated for multiple
Keyword to search for in event names, descriptions, or attractions (e.g., 'rock', 'Hamilton')
Geolocation filter as 'latitude,longitude' (use with radius and unit)
Filter by venue ID(s). Comma-separated for multiple
Filter events by geohash (alternative to latlong)
Filter by Ticketmaster market ID
Filter by segment ID(s) - highest classification level (Music, Sports, Arts & Theatre, etc.). Comma-separated for multiple
Filter by US state code (2-letter abbreviation)
Filter by event subtype ID(s). Comma-separated for multiple
Filter events by postal code or zipcode
Filter by promoter ID
Filter by subgenre ID(s). Comma-separated for multiple
Filter by ISO 3166 country code (2-letter)
Filter events starting on or before this date-time (ISO-8601 format with timezone)
Filter by segment name (e.g., 'Music', 'Sports', 'Arts & Theatre')
Filter by attraction ID(s). Comma-separated for multiple (e.g., 'K8vZ9172A1' for a specific artist/team)
Filter family-friendly events. 'yes'=include all, 'no'=exclude family events, 'only'=only family events
Filter events starting on or after this date-time (ISO-8601 format with timezone, e.g., '2026-03-01T00:00:00Z')
Filter by classification ID(s). Comma-separated for multiple. Supports negative filtering with '-' prefix
Include spell check suggestions for keywords. 'yes' or 'no'. Default: 'no'
Filter events with onsale end date/time on or before this date (ISO-8601 format)
Filter by classification name (segment/genre/subgenre). Supports negative filtering with '-' prefix (e.g., '-music' to exclude music)
Filter events with onsale start date/time on or after this date (ISO-8601 format)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_GENRE_DETAILSTool to retrieve detailed information about a specific genre. Use when you need metadata for a single genre before filtering events by genre.
Input parameters
Unique identifier of the genre. Use TICKETMASTER_GET_CLASSIFICATIONS to discover valid genre IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_SECTION_MAP_IMAGETool to retrieve the section map image for an event showing venue layout. Use when you need a visual representation of a venue's seating sections for a specific event. Optionally highlights specific sections or seats.
Input parameters
Application context for the map rendering (e.g., TOPPICKS for highlighting top pick sections)
The unique event identifier for which to retrieve the section map image
Specific seat or place identifier to highlight on the map
System identifier (e.g., HOST) to specify the ticketing system context
Specific venue sections to highlight on the map. Comma-separated for multiple sections
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_SEGMENT_DETAILSRetrieve detailed information about a specific Ticketmaster event segment, including all associated genres and subgenres. Segments are the top-level classification categories for events (e.g., Music, Sports, Arts & Theatre, Family, Film, Miscellaneous). This action returns the segment's metadata along with a complete list of genres and their subgenres that fall under this segment. Use this action after obtaining a segment ID from Get Classifications or from event classification data.
Input parameters
Unique identifier of the segment to retrieve. Segments represent primary event categories like Music (KZFzniwnSyZfZ7v7nJ), Sports (KZFzniwnSyZfZ7v7nE), or Arts & Theatre (KZFzniwnSyZfZ7v7na). Obtain from Get Classifications or Get Events actions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_SUBGENRE_DETAILSTool to retrieve detailed information about a specific subgenre. Use when you have a subgenre ID and need its details.
Input parameters
Unique identifier of the subgenre to retrieve
Locale in which to return results (e.g., en-us)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_SUGGESTIONS2Get advanced auto-complete search suggestions from Ticketmaster's Discovery API. Returns matching attractions (artists, teams, performers), venues (concert halls, stadiums, theaters), and events based on search criteria with extensive filtering options. Use this when you need more control over suggestions including location filtering, source filtering, fuzzy matching, and spell checking. Perfect for implementing type-ahead search functionality with advanced filters or helping users discover entertainment options based on location, segment, and other criteria.
Input parameters
Size of every entity returned in the response (number of suggestions per entity type). Default: 5
Unit of the radius. Options: miles or km. Default: miles
The locale in ISO code format. Multiple comma-separated values can be provided. When omitting the country part of the code (e.g. only 'en' or 'fr') then the first matching locale is used. When using a '*' it matches all locales. '*' can only be used at the end (e.g. 'en-us,en,*'). Default: en
Radius of the area in which we want to search for events. Used with latlong or geoPoint. Default: 100
Filter entities by its source name. Options: ticketmaster, universe, frontgate, tmr
Keyword to search on. Use partial keywords to get auto-complete suggestions (e.g., 'rock', 'jazz', 'broadway')
Filter events by latitude and longitude (format: 'lat,long' e.g., '34.0522,-118.2437'). Note: This filter is deprecated and may be removed in a future release, please use geoPoint instead
Filter events by geoHash (alternative to latlong). Use this instead of deprecated latlong parameter
Filter suggestions by segment ID (e.g., 'KZFzniwnSyZfZ7v7nJ' for Music segment)
Set to 'yes' to include events with date to be announced (TBA). Default: 'no' if date parameter sent, 'yes' otherwise. Options: yes, no, only
Set to 'yes' to include events with a date to be defined (TBD). Default: 'no' if date parameter sent, 'yes' otherwise. Options: yes, no, only
Filter suggestions by country code (ISO 3166-1 alpha-2, e.g., 'US', 'CA', 'GB')
Set to 'yes' to include fuzzy matches in the search. This has performance impact. Default: no
Filter events to clientName. Use to restrict results to specific client visibility
Set to 'yes' to include spell check suggestions in the response. Default: no
Set to 'yes' if you want to display licensed content. Default: no
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_VENUE_DETAILS2Tool to retrieve comprehensive details about a specific venue by ID. Use when you need detailed venue information including location, box office info, images, and social media data.
Input parameters
ID of the venue to retrieve details for
The locale in ISO code format. Multiple comma-separated values can be provided. When omitting the country part of the code (e.g. only 'en' or 'fr') then the first matching locale is used. When using a '*' it matches all locales. '*' can only be used at the end (e.g. 'en-us,en,*')
Enum for includeLicensedContent parameter.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TICKETMASTER_GET_VENUESTool to retrieve a list of venues based on specified criteria. Use when you need venue details by name, location, or ID.
Input parameters
Venue ID or comma-separated list of IDs
Filter by city name
Page number (default 0)
Number of results per page (default 20, max 200)
Sort order, e.g., 'name' or 'name,desc'
Filter by DMA ID or comma-separated list of IDs
Search radius in miles
Search by venue keyword
Latitude and longitude in format 'lat,long'
Filter by state code
Filter by postal code (max length 16)
Filter by 2-letter country code
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 80 agents privately built on Nagent that already use Ticketmaster.
Build on Nagent
Connect Ticketmaster to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Ticketmaster, and click "Connect Now." You'll authenticate with API_KEY, OAUTH2 — Nagent handles credential storage and refresh automatically. Once connected, Ticketmaster is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Ticketmaster is connected, you configure its 15 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Ticketmaster steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Ticketmaster event fires, the agent kicks off automatically.
Every Ticketmaster action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Ticketmaster ships with 15 pre-built event management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Ticketmaster together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Ticketmaster-based workflows tailored to your business.