Skip to main content

Authorization

Follow this guide to create a new Ticketmaster credential that will allow Nexla to authenticate to and exchange data with your Ticketmaster account.
ticketmaster_api_auth.png

Ticketmaster

Prerequisites​

Before creating a Ticketmaster credential, you need to obtain your API URL, Vendor, DSN (Data Source Name), CRM ID (icmcrmId), and API Key Value from your Ticketmaster account. Ticketmaster uses API key authentication for all API requests, with the API key sent in the apikey header.

To obtain your Ticketmaster credentials, follow these steps:

  1. Sign in to your Ticketmaster account using your administrator credentials.

  2. Navigate to your account settings or API management section in the Ticketmaster interface.

  3. Look for the API or Integration section in your account settings, or navigate to Settings > API or Admin > API Settings.

  4. If you don't have API credentials yet, look for the option to create or register an API application or integration.

  5. Configure your API integration settings:

    • Enter a name for the integration (e.g., "Nexla Integration")
    • Review and select the permissions or scopes for the integration (if applicable)

  6. After the integration is created, you will be provided with your API Key Value. Copy the API key immediately, as it may not be accessible again after you navigate away from the page.

  7. Your API URL is typically in the format https://app.ticketmaster.com/archtics-integration/external/v1/crm. This is the base URL for Ticketmaster API requests.

  8. Your Vendor is the vendor identifier provided by Ticketmaster for your integration. This should be obtained from your Ticketmaster account settings or API documentation.

  9. Your DSN (Data Source Name) is the data source name identifier provided by Ticketmaster for your integration. This should be obtained from your Ticketmaster account settings or API documentation.

  10. Your CRM ID (icmcrmId) is the CRM identifier provided by Ticketmaster for your integration. This should be obtained from your Ticketmaster account settings or API documentation.

  11. Store all credentials securely, as you will need them to configure your Nexla credential. The API Key Value, Vendor, DSN, and CRM ID are sensitive information and should be kept confidential.

The API Key Value is sent in the apikey header for all API requests to the Ticketmaster API. The API URL, Vendor, DSN, and CRM ID are used to construct API requests and identify your integration. The credentials authenticate your requests and grant access to Ticketmaster resources based on your account permissions. If your credentials are compromised, you should immediately revoke them in your Ticketmaster account settings and generate new ones. For detailed information about API authentication, credential management, and available endpoints, refer to the Ticketmaster API documentation.

Create a Ticketmaster Credential​

  • To create a new Ticketmaster credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Ticketmaster

TicketmasterCred.png

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

API Key Authentication​

Ticketmaster uses API key authentication for all API requests. The API Key Value is sent in the apikey header, and the API URL, Vendor, DSN, and CRM ID are used to construct API requests.

  1. Enter your Ticketmaster API URL in the API URL field. This is typically in the format https://app.ticketmaster.com/archtics-integration/external/v1/crm. The API URL is used as the base URL for all API requests to the Ticketmaster API.

  2. Enter your Ticketmaster Vendor in the Vendor field. This is the vendor identifier provided by Ticketmaster for your integration. The Vendor is used to identify your integration in API requests.

  3. Enter your Ticketmaster DSN (Data Source Name) in the DSN field. This is the data source name identifier provided by Ticketmaster for your integration. The DSN is sent in the DSN header for all API requests to the Ticketmaster API.

  4. Enter your Ticketmaster CRM ID (icmcrmId) in the CRM ID field. This is the CRM identifier provided by Ticketmaster for your integration. The CRM ID is sent in the icmcrmId header for all API requests to the Ticketmaster API.

  5. Enter your Ticketmaster API Key Value in the API Key Value field. This is the API key you obtained from your Ticketmaster account settings (Settings > API or Admin > API Settings) when creating your API integration. The API Key Value is sent in the apikey header for all API requests to the Ticketmaster API. The API Key Value is sensitive information and must be kept confidential.

    Your Ticketmaster API credentials can be found in your Ticketmaster account settings under Settings > API or Admin > API Settings. The API Key Value is generated when you create an API integration. The API URL, Vendor, DSN, and CRM ID are provided by Ticketmaster for your integration.

    The API Key Value is sent in the apikey header for all API requests to the Ticketmaster API. The API URL, Vendor, DSN, and CRM ID are used to construct API requests and identify your integration. The DSN and CRM ID are sent in the DSN and icmcrmId headers respectively.

    If your credentials are compromised, you should immediately revoke them in your Ticketmaster account settings and generate new ones. The credentials provide access to your Ticketmaster account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

    For detailed information about API authentication, credential management, and available endpoints, see the Ticketmaster API documentation.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.