# 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 `400` errors for bad paging values on `GET /events`.** A `page`, `per_page` or `venue_id` that is not plain digits now answers `400 invalid_page`, `400 invalid_per_page` or `400 invalid_venue_id` instead of `502 upstream_error`. See [Pagination](https://docs.bettertickets.com/pagination.md).
- **`404` instead of `502` for events and ticket types that are not available.**
  - `GET /events/{id}/locations` answers `404 event_not_found` for an event that does not exist or whose sales have closed.
  - `GET /locations/{id}/availability` answers `404 location_not_found` for 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}/locations` now answers `404 event_not_found` for a test event, like the other event operations. See [Test vs Live](https://docs.bettertickets.com/test-vs-live.md).
- **Stricter ids.** `GET /events/{id}/locations` and `GET /locations/{id}/availability` take plain digits only; values such as `5.0` or `1e1` answer `400 invalid_event_id` or `400 invalid_location_id`.
- **`401 invalid_api_key` now always means the key was refused.** When BetterTickets cannot check a key for a moment, the call answers `503 auth_unavailable` with `Retry-After: 5` instead of `401`. Wait `Retry-After` seconds between attempts; retrying faster gets `429 partner_rate_limited`. See [Authentication & Keys](https://docs.bettertickets.com/authentication.md).
- **Retry hints on `503` errors.** `auth_unavailable` and most `FEATURE_GATE_UNAVAILABLE` answers carry a `Retry-After` header plus `retryable` and `retry_after_seconds` in the body. On Custom Lists calls, `FEATURE_GATE_UNAVAILABLE` can still arrive as a bare `{ "error": "FEATURE_GATE_UNAVAILABLE" }`; when there is no `Retry-After`, wait 5 seconds. See [Retrying](https://docs.bettertickets.com/errors#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 `GET` and 30 `POST` per minute, and repeated requests with a missing or invalid key from one IP address get `429 partner_rate_limited` instead of `401`. See [Rate Limits](https://docs.bettertickets.com/rate-limits.md).
- **Clearer retry guidance.** `request_refused` is not retryable; contact BetterTickets if it persists. An unexpected `500` is retryable with backoff. See [Retrying](https://docs.bettertickets.com/errors#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](https://docs.bettertickets.com/llms.txt), [/llms-full.txt](https://docs.bettertickets.com/llms-full.txt) and the [OpenAPI 3.1 spec](https://docs.bettertickets.com/openapi.json).
- **v1 operations documented:**
  - `GET /events`
  - `GET /events/{id}`
  - `GET /events/{id}/locations`
  - `GET /locations/{id}/availability`
  - `GET /lists/{id}/rows`
  - `POST /lists/{id}/rows`
