Azure API Management doesn't prescribe a single approach to versioning, but instead provides several options. Versioning schemesĭifferent API developers have different requirements for versioning. Get started with versions by following our walkthrough. Take an existing (non-versioned) API, and create a new version of it without breaking existing clients.Show your API versions grouped together on the developer portal.Use any string value you wish to identify your version, which could be a number, a date, or a name.Use a path, query string, or header to differentiate between versions.Publish multiple versions of your API at the same time.Two different API versions might have different sets of operations and different policies. ![]() ![]() Versions are differentiated through a version identifier (which is any string value you choose), and a versioning scheme allows clients to identify which version of an API they want to use.įor most purposes, each API version can be considered its own independent API. Clients can choose to use your new API version when they're ready, while existing clients continue to use an older version. You can use versions to handle breaking changes in your API safely. Versions allow you to present groups of related APIs to your developers.
0 Comments
Leave a Reply. |