#Test vs Live
BetterTickets issues two kinds of key. Both use the same base URL:
https://app.bettertickets.com/api/partner/v1btk_test_… | btk_live_… | |
|---|---|---|
| Events, ticket types, availability | Same live data as a live key (read-only) | Live data |
| Test events | Not returned | Not returned |
| Custom List reads and writes | The list's Staging rows | The list's Production rows |
| Scopes, rate limits, errors | Same | Same |
#Events and availability
Event, ticket type and availability calls are read-only, so a test key simply sees the same live events, prices and availability as a live key. Nothing you read reserves or changes anything.
Events marked as test events in BetterTickets are not returned, for either kind of key:
| Operation | For a test event |
|---|---|
GET /events | Not listed |
GET /events/{id} | 404 event_not_found |
GET /events/{id}/locations | 404 event_not_found |
GET /locations/{id}/availability | 404 location_not_found |
#Custom Lists
Each Custom List keeps two separate data sets:
- Staging — read and written by
btk_test_keys. Use it to build and test your integration. - Production — read and written by
btk_live_keys. These are the rows your live automations use.
A list holds at most 50,000 rows per data set. Production reads answer 404 row_not_found while the list's Production switch is off.
#Going live
- Build and test against Staging with your
btk_test_key. - Ask your BetterTickets contact for a
btk_live_key with the same scopes. - Swap the key in your server's configuration. No URL changes are needed.