The right way to turn off your old APIs

All things come to an end, even HTTP APIs. However great your API may be today, one day you’ll want to release a completely new version, an improved but incompatible endpoint, a new parameter that solves the same problem better, or to shut down your API entirely. Your current API will not be live forever.

Inconveniently though, your API has clients. If you shut down endpoints, parameters, or entire APIs without properly warning them then they’re going to be very unhappy.

How do you shut down your APIs safely, making it at easy as possible for your users?

There are right ways to do this, including two new draft headers being standardized by the exciting new IETF “Building Blocks for HTTP APIs” working group, designed to help with this exact process. Let’s take a look.

This thread was posted by one of our members via one of our news source trackers.

Corresponding tweet for this thread:

https://twitter.com/dev_talk/status/1352903704060579840

Share link for this tweet.