V1 overview¶
V1 retires on January 15, 2027
Migrate to V2 before that date. The migration guide lists every route, field and ID change.
This page is for teams that still call /api/v1/. It explains what V1 is, which guides
still apply, and where to find V1 details. New integrations start with V2: see
Getting started.
What retires and when¶
Use the table to find the date that applies to the routes you call.
| Routes | Removal date |
|---|---|
Legacy V1 routes outside /api/v1/management/: bookings, members, contracts, billing_plans, payment_packs, consumer_payment_packs. Replacements are in the migration guide |
November 30, 2026 |
All other V1 routes, including /api/v1/management/ |
January 15, 2027 |
Which guides apply to V1¶
Read the table to see which guides cover V1 and which have a V1 version.
| Topic | V1 guide |
|---|---|
| Authentication, headers, errors, rate limits | The shared guides apply to both versions: Authentication, Headers and tenant context, Errors and status codes, Rate limits and bulk data sync |
| Pagination, ordering and filters | Pagination and filtering (V1) |
| Resource names, IDs and legacy route names | Data model and terminology (V1) |
| Endpoint details | API reference V1 |
| Moving to V2 | Migrate from V1 to V2 |
The shared guides show V2 paths in their examples. Replace /api/v2/ with /api/v1/ and
use the V1 field names from the V1 reference.
Webhooks and MCP¶
MCP tools use the V2 contract, so this overview does not apply to them. Webhook payloads use V1 only for registrations created before the V2 release. Registrations created after it use V2, even when you create them through a V1 route. See the version table in Getting started.