Docs / Data sources / Ticket Tailor

Ticket Tailor

Business software

Built when you ask for it

Sync Ticket Tailor event, order, and ticket data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Ticket Tailor connector syncs your event ticketing data into analytics-ready tables in your data warehouse. Pull events, orders, and issued tickets from the Ticket Tailor API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Events
  • Orders
  • Issued tickets

How it gets built

  1. Choose Ticket Tailor when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Ticket Tailor's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Ticket Tailor itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API key (Basic Auth). API keys are created per box office at app.tickettailor.com/box-office/api after signing up for a free account.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Ticket Tailor connector?
Not as a finished connector yet. Ingest builds it from Ticket Tailor's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Ticket Tailor data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Ticket Tailor API documentation: https://developers.tickettailor.com/docs/api/ticket-tailor-api/

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Ticket Tailor