Ticketmaster integration

Quick start

Call Ticketmaster from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Ticketmaster's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "TICKETMASTER_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

OverSkill hosts the OAuth application for Ticketmaster. End-users click Connect on the integration card in your app, complete the OAuth flow with Ticketmaster, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: API_KEY, OAUTH2.

Available actions

15 actions exposed via the Ticketmaster integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• TICKETMASTER_EXECUTE_SEASON_TICKETING_COMMAND
• TICKETMASTER_GET_ATTRACTION_DETAILS2
• TICKETMASTER_GET_ATTRACTIONS
• TICKETMASTER_GET_CLASSIFICATION_DETAILS
• TICKETMASTER_GET_CLASSIFICATIONS
• TICKETMASTER_GET_EVENT_DETAILS
• TICKETMASTER_GET_EVENT_IMAGES
• TICKETMASTER_GET_EVENTS
• TICKETMASTER_GET_GENRE_DETAILS
• TICKETMASTER_GET_SECTION_MAP_IMAGE
• TICKETMASTER_GET_SEGMENT_DETAILS
• TICKETMASTER_GET_SUBGENRE_DETAILS