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
| Feature | Support | Notes |
|---|---|---|
| Backfill | ✅ | Custom backfill (up to 2 years) |
| Incremental | ✅ | Supported on Bookings, Tickets, Discounts, Refunds, Payments |
| API reliability | 🟠 | API does occasionally encounter errors |
Reports detail
| ⬇️ Report | 🔑 Incremental key | 🔑 Primary key | 📄 Link to API endpoint |
|---|---|---|---|
| Products | N/A | ID | List Products |
| Product Variants | N/A | ID | List Product Variants |
| Bookings | UPDATED_AT | ID | List Bookings |
| Tickets | BOOKING_UPDATED_AT | ID | List Booking Tickets |
| Discounts | BOOKING_UPDATED_AT | ID | List Booking Discounts |
| Refunds | CREATED_AT | ID | Get a Refund |
| Payments | CREATED_AT | ID | Get a Payment |
Refunds&PaymentsreportsFor 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,TicketsandDiscountsreports may result in duplicates, which need to be dealt with in a Transform.
Limitations
Incremental logic in
RefundsandPaymentsreportsThe 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.
Updated 27 days ago