OCAPI Versioning and Deprecation policy 20.8

This document describes the versioning and deprecation policy for the Open Commerce API (OCAPI). This policy is designed to

Version Creation and Deprecation

We create a new OCAPI version to release one or more of the following types of changes:

When we release a new OCAPI version, we deprecate the previous OCAPI version. We strongly encourage customers and developers to:

Version Numbers

OCAPI version numbers consist of the last two digits of the current year ("13" for 2013), a period (.), and consecutive numbers, starting with 1. For example, "13.1" is the first version released in 2013.

Different contexts require different version number syntax:

Version Lifecycle

Version State Support Description
Current Yes The newest version. Always develop new applications using the current version. We support each OCAPI version for at least two years, during which its feature set remains stable.
Deprecated Yes When we release a new OCAPI version, we deprecate the current OCAPI version. We ensure support, stability, and backward-compatibility for up to two years after the publish date.
Obsolete No Deprecated versions become obsolete two years after release. Obsolete versions can be deleted without further notice.

Notification

The B2C Commerce release notes contain information about new OCAPI versions.

OCAPI obsolete versions 13.x and 14.x will be end of life in 2020 and versions 15.x and 16.x in 2021. For dates and more information, see the OCAPI versioning and deprecation policy and this Knowledge Article.
X Privacy Update: We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used. By continuing to use this site you are giving us your consent to do this. Privacy Policy.