4
2
279
2025-06-01
Bookings API v1.5 Deprecated
Replaced by v2.0 with new pricing engine and group bookings
2025-01-15
Events API v1.0 Deprecated
Replaced by v2.1 with recurring events and improved filters
2026-06-30
Bookings API v1.5 Sunset
All v1.5 endpoints will return 410 Gone
2026-09-30
Events API v1.0 Sunset
All v1.0 endpoints will return 410 Gone
2026-12-01
Search API v1.x Deprecation (Planned)
v2.4 with vector search will replace v1.x
When calling a deprecated API, the response includes standard deprecation headers per RFC 8594.
// Response from a deprecated endpoint
HTTP/1.1 200 OK
Deprecation: true
Sunset: Sat, 30 Jun 2026 00:00:00 GMT
Link: </dev/lifecycle/migration>; rel="successor-version"
X-Deprecation-Notice: This API version is deprecated. Migrate to v2.0.
// SDK automatically logs warnings for deprecated API calls:
// [WARN] @eventzr/booking-client: Bookings API v1.5 is deprecated.
// Sunset: 2026-06-30. See: /dev/lifecycle/migration| Policy | Requirement |
|---|---|
| Minimum notice period | 6 months before sunset |
| Deprecation announcement | Email, dashboard banner, API headers |
| Migration guide | Published before deprecation date |
| SDK support | Deprecation warnings in SDK logs |
| Usage monitoring | Weekly reports for affected developers |
| Extension requests | Available for Enterprise customers |
| Sunset behavior | 410 Gone with migration link in body |
Configure how you receive deprecation notifications via the API or developer dashboard.
// Subscribe to deprecation notifications
POST /notify/v1/subscriptions
Authorization: Bearer <token>
x-tenant-id: <tenant-id>
{
"channel": "email",
"topics": ["api.deprecation", "api.sunset", "api.breaking-change"],
"frequency": "immediate" // or "daily-digest", "weekly-digest"
}