API Versioning

Selling Partner API supports versioning so that developers can integrate with changes and new features over time. This topic explains the Selling Partner API versioning system.

Versioning

Each individual API maintains an independent version. This allows changes to be introduced without impacting existing integrations. Multiple versions of an API can exist at the same time with different features in each version.

In 2021, we changed versions to a date-based system. The format is version-year-month-day [v2021-06-30]. Note that the version of the API is not necessarily when the API was released to general availability.

Previously, the version system was ordinal numbers [v0 or v1].

You may still see many APIs using the old versioning numbers. This does not mean that the API is outdated or that there have not been small changes made to the API since it's initial release. It only means that we have not yet transitioned that API to use the new versioning system.

Why do we use versions?

Our goal with API versions is to allow developers time to try and test new features and functionality before requiring integration. This allows you to plan development activity on a timeline that works for your business and customers.

Does everything remain static in a version after it's been released?

Not necessarily. There may be small, non-breaking changes made to an API that does not require a version increase. The include new error messages or responses, support for new marketplaces, and added parameters.

Changes will be documented in the Release Notes for each API as they occur.

Lifecycle of a version

Each API has its own development rhythm and lifecycle. Typically, a version will be available for a minimum of 1-year after it has been made publicly available in a General Release.

For more information, see The API Lifecycle.

Depending on the development activity and evolution of an API, it may be necessary to discontinue it after a new version has been released or a replacement API has been released. We will publicly announce when we plan to discontinue an API version on the Versions page.