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 | UPDATED_AT | ID | Get a Refund |
| Payments | UPDATED_AT | ID | Get a Payment |
| Bookings (by cancelled date) | CANCELLED_AT | ID | List Bookings |
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
TicketsandDiscountsreports' BackfillLong Backfill settings (e.g. 6 years) can cause errors or very long run times on these two reports and we suggest using shorter periods to avoid issues.
BookingsandBookings (by cancelled date)reportsThe
Bookingsreport uses UPDATED_AT field/column as it's incremental field. Unfortunately the API does not recognise a booking's cancellation as a factor that affects UPDATED_AT. This means you can miss cancelled bookings on incremental runs on theBookingsreport.The
Bookings (by cancelled date)uses CANCELLED_AT field/column as it's incremental field. This can allow you to run a separate report to collect the cancelled bookings and later combine the data if needed.
Updated 10 days ago