Once you have an API out in the wild (be it one that’s well designed, or one that grew organically), how do you evolve that API in the future? How do you take something everyone is using in a variety of ways, and distill those needs down into improvements?
This talk will walk through a recent major API version update we went through at PagerDuty from beginning to end. This will include details on what kinds of usage data we gathered, how we engaged with users of the API to understand what worked well and what didn’t, and how to break out of some of the existing antipatterns we had.
Audience members of this talk will be able to walk away with strategies they can apply to their own APIs (internal or external), testing patterns to consider, and ways to communicate engineering efforts in terms of business and customer value.