API Deprecation Notice
A complete, RFC-aligned deprecation notice body for an API endpoint, ready to paste into docs or an email.
More from Writing
What you get
A complete, RFC-aligned API deprecation notice body in text format, ready to paste into docs or an email, including all necessary details such as the endpoint, sunset date, and migration path.
Who it's for
- Software developers maintaining public APIs
- Technical writers documenting API changes
- DevOps engineers managing API lifecycle
- Product managers overseeing API development
Use cases
- Notifying users of an upcoming API endpoint removal
- Documenting changes to an API for internal stakeholders
- Providing a migration path for deprecated API endpoints
- Informing customers about API deprecation and sunset dates
- Updating API documentation to reflect changes
FAQ
what goes in an api deprecation notice
An API deprecation notice should include the endpoint being deprecated, the sunset date in ISO-8601 format, the migration path, and the version or date since which the endpoint has been deprecated. This notice should be concise, typically within 200 words, and follow RFC 8594 Sunset and RFC 9745 Deprecation conventions.
how do i write a polite api deprecation notice
To write a polite API deprecation notice, focus on providing clear, direct information about the deprecation, including the endpoint, sunset date, and migration path. Avoid using passive blame or overly technical language, and ensure the tone is direct and factual, without being aggressive or saccharine.
what is the structure of an api deprecation notice
The structure of an API deprecation notice typically includes the endpoint being deprecated, the version or date since which it has been deprecated, the sunset date in ISO-8601 format, and the migration path or replacement endpoint. This information should be presented in a clear, concise manner, following established conventions such as RFC 8594 and RFC 9745.
how do i provide a migration path for a deprecated api endpoint
To provide a migration path for a deprecated API endpoint, include a clear description of the replacement endpoint or a link to migration documentation in your deprecation notice. This helps users understand how to transition to the new endpoint and minimizes disruption to their applications.
Last updated: 2026-06-28