Deprecation
Infobip follows a structured process when retiring API endpoints to give you time to migrate your integrations.
Terminology
- Deprecated — An endpoint that is obsolete and not recommended for use, but remains operational. It may continue working indefinitely or be discontinued at a scheduled date.
- Sunset — An endpoint that has been permanently shut down and is no longer operational.
How you'll be notified
When an endpoint is deprecated, you'll see signals in multiple places:
- OpenAPI specification — The endpoint is marked with the standard
deprecatedflag and includes deprecation metadata: deprecation date, planned sunset date, and successor endpoint if available. - API response headers — Calls to deprecated endpoints return headers indicating the deprecation and sunset dates, plus links to the replacement endpoint and deprecation policy.
- Documentation — Both the deprecated and replacement versions are documented to help you compare differences. The deprecated version remains visible until its sunset date.
- Email notifications — If you're actively using a deprecated endpoint, you'll receive direct communication about the timeline and migration path.
What to expect before shutdown
If an endpoint is approaching its sunset date and you haven't migrated, you may experience brownout periods — brief, scheduled outages designed to surface any overlooked dependencies.
After the sunset date, the endpoint returns HTTP 410 Gone.
To prepare your integration for a migration, see Migrating existing resources.
Related
Backwards compatibility
What Infobip commits to within a MAJOR version and how to build resilient integrations.
Migrating existing resources
Steps and contacts for moving your integration from a deprecated endpoint to its replacement.