Skip to content
  • There are no suggestions because the search field is empty.

Ticketmaster Integration Set Up Steps

Internal Guide: Ticketmaster Integration Process

This guide outlines how our team should guide customers through the Ticketmaster integration and the internal steps required to complete the integration once Ticketmaster responds.

This integration requires external approval from Ticketmaster and an engineering build on our side, so clear communication with the customer is important.

Part 1 — How to Guide the Customer

1. Confirm the Integration Is Included

Before starting, confirm that Ticketmaster integration is included in the customer’s contract, as it is a paid integration.

If it is not included:

  • Loop in Sales or Account Management before proceeding.

2. Instruct the Customer to Request SDK Access

The customer must request the Ticketmaster SDK directly from Ticketmaster.

Explain that this request must come from someone authorized at their organization (ex: director, administrator, or technical lead).

Ask them to send an email to:

Provide this template:

 
I, [NAME], [TITLE], at [INSTITUTION], hereby approve Ticketmaster to provide to Snap! Mobile, Inc. the Ticketmaster SDK with access to the [INSTITUTION] database.

The [INSTITUTION] Archtics database name/DSN is [NAME] and site ID is [ID].

If I choose [VENUE], then all events for the venue (team plus non-team events) will be shown.

I also understand that this integration will be kept active until myself or someone else from [INSTITUTION] emails the Ticketmaster integration team to deactivate the integration.

Please let me know if you have any questions.

Thank you,
[NAME]
[DATE]
 

3. Set Expectations with the Customer

Let the customer know:

  • Ticketmaster will review the request.

  • They may follow up with questions.

  • Ticketmaster will provide SDK credentials needed to complete the integration.

Ticketmaster will typically return:

  • iOS Consumer Key

  • Android Consumer Key

Once the customer receives these, they should send them to Support.

Part 2 — Internal Steps After Ticketmaster Responds

Once the customer provides the Ticketmaster credentials:

1. Verify Required Credentials

Confirm that the following were provided:

  • iOS Consumer Key

  • Android Consumer Key

If anything is missing, ask the customer to follow up with Ticketmaster.

2. Create an Engineering Ticket

Create a ticket for engineering that includes:

  • Customer name

  • Organization / institution name

  • Archtics database name / DSN

  • Site ID

  • iOS Consumer Key

  • Android Consumer Key

  • Any Ticketmaster email threads if relevant

Note that this requires a new build to implement the SDK credentials.

3. Engineering Implementation

Engineering will:

  • Configure the Ticketmaster SDK

  • Add the provided consumer keys

  • Include the integration in the next build of the application

4. Notify the Customer

Once engineering confirms the integration has been implemented:

  • Notify the customer that the integration is live.

  • Confirm they can begin using Ticketmaster events within the platform.

Key Notes for Internal Teams

  • This integration cannot be completed until Ticketmaster provides SDK credentials.

  • The integration requires an app build and cannot be enabled instantly.

  • The integration remains active indefinitely until the organization requests deactivation from Ticketmaster.

Quick Workflow Summary

Customer → sends approval email to Ticketmaster
Ticketmaster → provides SDK credentials
Customer → sends credentials to Support
Support → creates engineering ticket
Engineering → implements SDK and releases new build
Support → confirms activation with customer