This page contains information about how Thrive deprecates and eventually sunsets (retires and removes from service) API versions and specific endpoints.
We work hard to keep our API stable and predictable so your integrations don't break unexpectedly. This policy explains how we handle necessary changes to improve performance, security, or design, and what you can expect when an endpoint or version is deprecated.
Our Promise
We’ll always aim to give you at least 3 months' notice before we remove or sunset an API version or endpoint.
During that window, the affected endpoints will remain fully operational, but they will only receive maintenance and security updates—no new features or incremental improvements.
Important:
In rare cases, such as urgent security fixes or compliance requirements, we may need to remove or modify an endpoint immediately. When this happens, we’ll communicate as quickly and transparently as possible through the same channels outlined below.
Notification Channels
When an API version or endpoint is scheduled for deprecation, we’ll make sure you hear about it in multiple ways:
Email notifications.
Posts on Thrive Tribe.
Direct contact from your account director.
Each notice will include:
The affected API version(s) or endpoint(s).
The date the deprecation starts.
The expected removal (sunset) date.
Migration guidance or links to replacement endpoints.
What Happens During Deprecation
Timing | Description |
|---|---|
Day 0 (Announcement) | Deprecation is officially announced via email, Thrive Tribe, and account directors. |
Months 0 to 3 (Deprecation Period) | The endpoint(s) remain active and operational, receiving only maintenance and security fixes. |
Sunset Date (After 3 Months) | The endpoint or version is permanently removed from service. Requests will fail with a clear error response. |
Example Deprecation Timeline
Announcement | Deprecation Window (3 Months) | Sunset Date (Retied) |
|---|---|---|
1st November 2025 | 1st November 2025 — 31st January 2026 (Endpoint still active and operational) | 1st February 2026 (Endpoint removed from service) |
Versioning and breaking changes
Information about our approach to versioning and breaking changes, including developer guidance, can be found in our versioning and breaking changes page.
Versioning and Breaking Changes
Information about our approach to versioning and breaking changes, including developer guidance, can be found in the Versioning and Breaking Changes page.