Menu

1 / 2

Azure API Management Developer Portal and API Versioning: Version Sets Without Breaking Callers

DEV Community: azure·Martin Oehlert·11 days ago
#h816GEci
#devtoazure#devto#dev#portal#version
Reading 0:00
15s threshold

How do you ship a breaking change to the order API without breaking the partners who already call it, when the next partner should find the API in the developer portal, read the docs and get a key without opening a ticket? The versioning half has a trap that decides the rest: API Management fixes the versioning scheme for every version in a version set the moment you add the first one, and the live API keeps its URL only if it stays the Original version. Give it a v1 identifier and every existing call stops matching. The short answer for the order API: path versioning, the live API kept as Original, v2 only for the breaking change, revisions for everything else, and two products so a free tier and partners get different limits and only partners need approval.

After Part 3 the order API is locked down and nobody can find it. There is one product, one subscription that Bicep created for a partner called Contoso Shop, and an Entra ID token check in front of every operation.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.