Phil, Mike, and Matt get together for a discussion about how to safely sunset an API endpoint with the end goal being deprecation. We take a look at why its important to be overly communicative about it, what an appropriate length of time is from announcement to deprecation and how you can do it in a way that doesn't make your team or external consumers angry. We talk about the HTTP Sunset Header and the potential HTTP Deprecation Header and how those can make the process of knowing when APIs are being deprecated a lot smoother. We also looked at a few popular JS libraries and discuss how they deprecated themselves. Show Notes
deprecation noticeIEFT HTTP Sunset Header Field RFCIEFT HTTP Deprecation Header Draft
botching a feature deprecationSponsor
Interested in sponsoring this podcast to get the word out about your API product to our listeners? Drop us a line at @apisyouwonthate
on twitter and lets get it set up!
★ Support this podcast on Patreon ★