#Changelog
The API is versioned in the path (/api/partner/v1). New operations, optional parameters, response fields and error codes can appear within v1, so build your client to ignore fields and error codes it does not know.
#2026-11-18
Spec version 1.0.1. Clearer errors and stricter checks; nothing was removed.
- Clear
400errors for bad paging values onGET /events. Apage,per_pageorvenue_idthat is not plain digits now answers400 invalid_page,400 invalid_per_pageor400 invalid_venue_idinstead of502 upstream_error. See Pagination. 404instead of502for events and ticket types that are not available.GET /events/{id}/locationsanswers404 event_not_foundfor an event that does not exist or whose sales have closed.GET /locations/{id}/availabilityanswers404 location_not_foundfor a ticket type that does not exist, is not sold on its own, or whose event's sales have closed.
- Test events are hidden everywhere.
GET /events/{id}/locationsnow answers404 event_not_foundfor a test event, like the other event operations. See Test vs Live. - Stricter ids.
GET /events/{id}/locationsandGET /locations/{id}/availabilitytake plain digits only; values such as5.0or1e1answer400 invalid_event_idor400 invalid_location_id. 401 invalid_api_keynow always means the key was refused. When BetterTickets cannot check a key for a moment, the call answers503 auth_unavailablewithRetry-After: 5instead of401. WaitRetry-Afterseconds between attempts; retrying faster gets429 partner_rate_limited. See Authentication & Keys.- Retry hints on
503errors.auth_unavailableand mostFEATURE_GATE_UNAVAILABLEanswers carry aRetry-Afterheader plusretryableandretry_after_secondsin the body. On Custom Lists calls,FEATURE_GATE_UNAVAILABLEcan still arrive as a bare{ "error": "FEATURE_GATE_UNAVAILABLE" }; when there is noRetry-After, wait 5 seconds. See Retrying. - Event responses contain only the documented fields. Every documented field is unchanged.
- Rate limits documented in full. Requests from one IP address, across all keys, are limited to about 60
GETand 30POSTper minute, and repeated requests with a missing or invalid key from one IP address get429 partner_rate_limitedinstead of401. See Rate Limits. - Clearer retry guidance.
request_refusedis not retryable; contact BetterTickets if it persists. An unexpected500is retryable with backoff. See Retrying. - Known issues resolved. Every item on the former Known Issues list is fixed, and the list has been removed.
#November 2026
- Published: public developer docs at docs.bettertickets.com, with a Markdown twin of every page, /llms.txt, /llms-full.txt and the OpenAPI 3.1 spec.
- v1 operations documented:
GET /eventsGET /events/{id}GET /events/{id}/locationsGET /locations/{id}/availabilityGET /lists/{id}/rowsPOST /lists/{id}/rows