Ticket Tailor is a low-fee event ticketing platform for selling tickets and managing attendees. Its REST API exposes box office data such as events, event series, orders, discounts, check-ins, holds, and issued tickets, and lets you create and update ticketing resources programmatically.
Power end-to-end data operations for your TicketTailor API with Nexla. Our bi-directional TicketTailor connector is purpose-built for TicketTailor, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to TicketTailor or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your TicketTailor workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Ticket Tailor credential, you need an API key from your Ticket Tailor box office. The Ticket Tailor API uses HTTP Basic authentication, where the API key is supplied as the username and the password is left empty. Each API key is scoped to a single box office and grants access only to that box office's data.
To obtain your API key, follow these steps:
Sign in to your Ticket Tailor account.
Open your box office API settings at https://app.tickettailor.com/box-office/api.
Generate or copy an existing API key for the box office you want to connect. Ticket Tailor API keys begin with a sk_ prefix.
Store the API key securely. You will supply it as the username when creating your Nexla credential, and leave the password blank.
All requests are made over HTTPS. For more detail on authentication and available resources, see the Ticket Tailor API documentation.
Your Ticket Tailor API key, used as the Basic authentication username. Ticket Tailor API keys begin with a sk_ prefix and are found in your box office API settings.
Password
Yes
Yes
Your password. For Ticket Tailor Basic authentication, the API key is supplied as the username and the password is left empty.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Ticket Tailor API key in the Username Or API Key field. This is the key found in your box office API settings and is sent as the Basic authentication username.
Leave the Password field empty. Ticket Tailor authenticates using the API key as the username with an empty password.
Each Ticket Tailor API key is scoped to a single box office and grants access only to that box office's data. If a key is compromised, revoke it in your Ticket Tailor box office API settings and generate a new one.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the TicketTailor connector tile, then select the credential that will be used to connect to Ticket Tailor, and click Next; or, create a new TicketTailor credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Ticket Tailor endpoints. 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.
[Rest API] Ping the API
Ping the API.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Get box office overview
Get box office overview.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Returns a list of events belonging to the box office
Returns a list of events belonging to the box office.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Retrieve a specific event
Retrieve a specific event.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Returns a list of event series
Returns a list of event series.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Retrieve a single event series
Retrieve a single event series.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Get event series override list
Get event series override list.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Get event series waitlist signup list
Get event series waitlist signup list.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Returns a list of orders belonging to box office
Returns a list of orders belonging to box office.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Retrieve a single order by ID
Retrieve a single order by ID.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Returns a list of paginated discounts
Returns a list of paginated discounts.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Retrieve a single discount
Retrieve a single discount.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Returns a paginated list of check-ins
Returns a paginated list of check-ins.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Get hold list
Get hold list.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Retrieve a single hold
Retrieve a single hold.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Get all issued tickets
Get all issued tickets.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
[Rest API] Retrieve a single issued ticket
Retrieve a single issued ticket.
Select this endpoint template to configure a source that reads from this Ticket Tailor endpoint. Click the Test button after configuring to preview a sample of the data that will be fetched.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
TicketTailor data sources can also be manually configured to ingest data from any valid Ticket Tailor API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new TicketTailor data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the TicketTailor destination, and select the Send to Destination option from the menu. Select the TicketTailor connector from the list of available destination connectors, then select the credential that will be used to connect to Ticket Tailor, and click Next; or, create a new TicketTailor credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Ticket Tailor endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Create an event series bundle
Create an event series bundle.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Create a ticket type for an event series
Create a ticket type for an event series.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Update a ticket type
Update a ticket type.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Delete a ticket type
Delete a ticket type.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Create a ticket group for an event series
Create a ticket group for an event series.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Modify an existing order
Modify an existing order.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Mark an offline payment as received
Mark an offline payment as received.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Create a discount code
Create a discount code.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Update a discount
Update a discount.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Remove a discount
Remove a discount.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Create a check in
Create a check in.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Create a hold
Create a hold.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
[Rest API] Delete a hold
Delete a hold.
Select this endpoint template to configure a destination that writes to this Ticket Tailor endpoint. Each record from your Nexset is sent as a separate request in the format expected by the Ticket Tailor API.
TicketTailor destinations can also be manually configured to send data to any valid Ticket Tailor API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Ticket Tailor endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Ticket Tailor endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
