Skip to main content

Data Source

Follow the instructions below to create a new data flow that ingests data from a Ticketmaster source in Nexla.
ticketmaster_api.png

Ticketmaster

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Ticketmaster connector tile from the list of available connectors. Then, select the credential that will be used to connect to your Ticketmaster account, and click Next; or, create a new Ticketmaster credential for use in this flow.

  3. In Nexla, Ticketmaster data sources can be created using pre-built endpoint templates, which expedite source setup for common Ticketmaster endpoints. Each template is designed specifically for the corresponding Ticketmaster endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Ticketmaster sources can also be configured manually, allowing you to ingest data from Ticketmaster endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Ticketmaster endpoints. Each template is designed specifically for the corresponding Ticketmaster endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    List all records

    This endpoint template returns a list of records of a selected resource from your Ticketmaster account. Use this template when you need to access CRM resource data, ticket information, or event data for analysis, reporting, or integration purposes.

    • Enter the Name of the CRM Resource in the Name of the CRM Resource field. This should be the type of CRM resource you want to retrieve (e.g., availSeats, events, tickets, etc.). The CRM Resource Type determines which type of records will be retrieved. Available resource types include availSeats, events, tickets, and other CRM resources. The endpoint uses incrementing page-based pagination to handle large datasets efficiently, returning up to 100 records per page by default, starting from page 0.

    This endpoint returns a list of records of a selected resource from your Ticketmaster account, including resource IDs, names, and other resource metadata. The endpoint uses incrementing page-based pagination with page and size parameters to handle large datasets efficiently. Nexla will automatically fetch subsequent pages of data by incrementing the page parameter, starting from page 0.

    The CRM Resource Type can be selected from available options (e.g., availSeats, events, tickets, etc.). The endpoint uses the API URL, Vendor, DSN, and CRM ID from your credential to construct the API request. For detailed information about CRM resources, API response structures, pagination, and available resource types, see the Ticketmaster API documentation.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Ticketmaster data sources can be manually configured to ingest data from any valid Ticketmaster API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Ticketmaster sources, such as sources that use chained API calls to fetch related data or sources that require custom query parameters or filters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Ticketmaster API from the Method pulldown menu. Ticketmaster API typically uses GET method for retrieving data from endpoints.

API Endpoint URL​

  1. Enter the URL of the Ticketmaster API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL to your Ticketmaster endpoint, using your API URL from the credential (e.g., {api_url}/{resource_type}?vendor={vendor}). Include any required path parameters and query parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The Ticketmaster API endpoint URL should use your API URL from the credential (typically https://app.ticketmaster.com/archtics-integration/external/v1/crm) and include the resource type path and vendor query parameter. You can test the endpoint using the Test button after configuring the URL.

Response Data Path​

  1. Enter the JSONPath expression in the Response Data Path field to specify which part of the API response should be treated as the relevant data by Nexla. For Ticketmaster API responses, use $._embedded.{resource_type}[*] to extract all items from the embedded resource array (e.g., $._embedded.availSeats[*], $._embedded.events[*]), or $[*] to extract all items from the response array, depending on your endpoint.

The JSONPath expression must correctly reference the structure of your Ticketmaster API response. Ticketmaster API responses typically have an _embedded object containing resource arrays. Ensure your JSONPath expression matches the structure returned by your specific endpoint. The JSONPath expression determines which data will be extracted and processed by Nexla.

Pagination (if applicable)​

  1. If your endpoint supports pagination, configure the pagination settings in the Pagination section. Ticketmaster API uses incrementing page-based pagination with page and size parameters for most endpoints, starting from page 0. Select the pagination type that matches your endpoint's pagination mechanism.

  2. Configure the pagination parameters based on your selected pagination type. For incrementing page-based pagination, specify the page parameter name (page), page size parameter name (size), and starting page number (typically 0).

Request Headers​

  1. If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., DSN:{dsn},icmcrmId:{crm_id}). The DSN and CRM ID from your credential are automatically included in the request headers.

You do not need to include headers already present in the credentials. Common headers like Authorization (apikey), DSN, and icmcrmId are typically handled automatically by Nexla based on your credential configuration.

Save the Data Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.