How APIs Use Versioning to Avoid Breaking Changes
from The API Podcast with Fexingo: REST, GraphQL, and Modern Web APIs Hosted by Fexingo
API versioning is one of those topics every developer has opinions about, but few agree on the right approach. In this episode, Lucas and Luna dig into the real trade-offs between URI versioning, header versioning, and content negotiation, using Stripe's v1 and v2 APIs as a concrete case study. They walk through what actually happened when Stripe released its second API version, how it handled migration, and what lessons any team can steal—whether you're building a public API or an internal one. Along the way, they unpack the idea of deprecation timelines, sunset headers, and why versioning isn't just a technical decision but a product one. If you've ever wrestled with whether to put the version in the URL or the header, or wondered why some APIs still break despite semver, this episode gives you a framework to think about it. No hype, just practical detail you can mention to a friend building their next API. #APIVersioning #RESTfulAPIs #StripeAPI #SemanticVersioning #TechPodcast #API #WebDevelopment #Developer #Backend #SoftwareEngineering #Tech #Business #ProductManagement #FexingoBusiness #BusinessPodcast #Technology #APIStrategy #DeveloperExperience Keep every episode free: buymeacoffee.com/fexingo
Embed this episode
No transcript yet.