Summary

At this point, you know what an API retirement process looks like. You know that retiring an API isn’t just turning it off. Instead, it might take as long as existing consumers need to adjust. You know why APIs are retired and how you can measure the factors that can influence your decision. You also know that understanding the cost behind maintaining your API is crucial to knowing when the right time for a retirement is. And knowing the right time is the first thing you need to communicate the API retirement. You know that you should begin by sharing why you’re retiring your API and giving plenty of time for all stakeholders to digest the information. You also know how to update existing information about your API in marketplaces to give new and existing visitors the news about its retirement. Additionally, you know how to drive an API product retrospective to learn what led to the retirement and improve your future actions. You know who to invite to the retrospective...