TicketingHub

Version 0.0.1

📘

Check out the TicketingHub API docs here for more information.

Set up


You will need to get your API key to get started. To get it, please reach out to your TicketingHub representative.

Features


FeatureSupportNotes
BackfillCustom backfill (up to 2 years)
IncrementalSupported on Bookings, Tickets, Discounts, Refunds, Payments
API reliability🟠API does occasionally encounter errors

Reports detail


⬇️ Report🔑 Incremental key🔑 Primary key📄 Link to API endpoint
ProductsN/AIDList Products
Product VariantsN/AIDList Product Variants
BookingsUPDATED_ATIDList Bookings
TicketsBOOKING_UPDATED_ATIDList Booking Tickets
DiscountsBOOKING_UPDATED_ATIDList Booking Discounts
RefundsCREATED_ATIDGet a Refund
PaymentsCREATED_ATIDGet a Payment

📘

Refunds & Payments reports

For these reports, you must provide a comma-separated list of IDs (of refund or payment IDs) on the extract setup page.

📘

Duplicates

Incremental runs on Bookings, Tickets and Discounts reports may result in duplicates, which need to be dealt with in a Transform.


Limitations


🚧

Incremental logic in Refunds and Payments reports

The incremental logic for Refunds and Payments reports relies on the CREATED_AT field. This means that there is a chance on incremental runs you might end up missing entries that have been updated.

To avoid missing data you can either run full backfills or if you want to run incrementally, you can do regular data reconciliations via an occasional full backfill.