#BetterTickets API
The BetterTickets API lets your own server read your account's events, ticket types and live availability, and read and update rows of your Custom Lists. It is a small, JSON-over-HTTPS REST API authenticated with a Bearer key.
Server-to-server only. Call the API from your backend. Browsers are refused (no CORS), so never put a key in a web page or mobile app.
#Base URL
https://app.bettertickets.com/api/partner/v1Test keys and live keys use the same base URL. See Test vs Live.
#Quickstart
- Ask your BetterTickets contact to turn on API access for your account and issue you an API key. You get a
btk_test_…key for building and abtk_live_…key for production. Until API access is on, every call answers403 partner_api_disabled. - Put the key in an environment variable on your server. The samples in these docs read it from
BETTERTICKETS_API_KEY:
export BETTERTICKETS_API_KEY=btk_test_…- Send it as a Bearer token and list your events:
curl https://app.bettertickets.com/api/partner/v1/events \
-H "Authorization: Bearer $BETTERTICKETS_API_KEY"A successful call answers 200 with a page of events (shortened; see List events for every field):
{
"itemsReceived": 1,
"curPage": 1,
"nextPage": null,
"items": [
{ "id": 1001, "name": "Summer Roots Festival 2027", "date": "2027-07-16", "is_sold_out": false }
]
}- Pick an event and list its ticket types. Replace
1001with anitems[].idfrom step 3:
curl https://app.bettertickets.com/api/partner/v1/events/1001/locations \
-H "Authorization: Bearer $BETTERTICKETS_API_KEY"- Check live availability right before you sell. Replace
2001with anitems[].idfrom the step 4 response:
curl "https://app.bettertickets.com/api/partner/v1/locations/2001/availability?requested_quantity=2" \
-H "Authorization: Bearer $BETTERTICKETS_API_KEY"#What you can do
| Resource | Operations | Scope |
|---|---|---|
| Events | List events, Get one event, List an event's ticket types | events:read |
| Availability | Get live availability of a ticket type | events:read |
| Custom Lists | Look up one list row, Add or update list rows | lists:read, lists:write |
#Conventions
- JSON in and out. Send
Content-Type: application/jsononPOST. Responses are JSON, and responses to supported methods carryCache-Control: no-store. Do not cache any response. - Money is in cents. A
priceof5000is $50.00. -1means unlimited in quantity fields such asavailable_quantityandeffective_available.- Ticket types are called locations in paths and field names. A location is one thing a buyer can pick for an event, for example GA, VIP, or a pickup stop.
- Timestamps. List row
added_atandupdated_atare epoch milliseconds. Eventdate,absolute_timeanddoors_timeare text as entered for the event; their format is not normalized. - Documented fields only. Responses can contain fields that are not documented here. They are not part of the API, may change or disappear without notice, and must not be relied on.
- Errors share one shape:
{ "error": "<code>", "message": "…" }. Branch onerror. See Errors.
#Typical flow
GET /eventsto find the event (filter by date, venue or text).GET /events/{id}/locationsto pick a ticket type and read its price.GET /locations/{id}/availabilityright before you sell, to confirmcan_fulfill.
Availability is read-only: nothing is reserved, so check it as close to the sale as you can.
#For AI tools
Every page has a Markdown twin at the same path plus .md. The whole site is also available as /llms.txt (index) and /llms-full.txt (everything in one file), and the spec as /openapi.json (OpenAPI 3.1).