Retire

The retirement of an API or specific version of an API is an inevitable thing and there should be a formal process in place to inform API producers about what the steps are in a process to retired, and set in motion the deprecation of an API, keeping an API or version of an API active for a specific amount of time, while acknowledging that at some point it will go away.

Does this provide what you need? Let us know by submitting issue!

As an API, or a specific version of an API approaches its end of life it is common to retire the API, setting expectations with consumers about the eventual deprecation of an API within a specific time period. The retirement of an API can involve updating documentation to reflect the retirement state of an API, adding a potential header that goes out with each API response, as well as sending out notifications and other communications with consumers that an API has reached the retirement stage. Retirement is the stage that signals to consumers that an API is still available for use, but will not be evolving forward anymore, and at some date in the near future it will eventually be deprecated.



Blueprints

Return to Main Page

This provides a link back to the home page if you need it.