Module 07 of 10

Versioning & Evolution

Lessons

About This Module

Once people depend on your API, every change carries risk. This module covers how to keep improving an API over time while the applications built on it keep working.

It starts with breaking vs non-breaking changes and how semantic versioning communicates them. From there it compares the common versioning strategies: putting the version in the URI, in a header, or in a query parameter, and the trade-offs of each. It also looks at planning for change, including deprecating old versions, giving consumers time to migrate, and designing so that fewer breaking changes are needed in the first place.

Watch the lessons in order, then continue on to GraphQL, gRPC & Beyond REST, where you'll see how other API styles approach the same design questions.

Lessons

4 videos
01

What is Semantic Versioning?

How MAJOR.MINOR.PATCH version numbers work and what they mean for API compatibility, including why consumers rely on all observable behavior (Hyrum’s Law).

02

API Versioning Strategies Explained

An overview of the most common ways to version an API so you can update and evolve it without breaking existing applications.

03

How API Versioning Prevents Breaks and Ensures Stability

Postman explains why versioning matters in enterprise environments, covering URI, header, and query parameter versioning.

04

4 Best Ways to Version Your REST APIs (Stop Breaking Clients!)

A walkthrough of four versioning strategies for REST APIs, including URI versioning, and how to stop changes from breaking old clients.