Salesforce B2C Commerce 24.7 > Open Commerce API 23.2 > OCAPI Usage 23.2

OCAPI versioning and deprecation policy 23.2

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

  • Be easy for customers and developers to understand
  • Allow Commerce Cloud Digital to make design changes to the API without affecting existing client applications
  • Allow Digital to delete outdated or unsupported features

Version creation and deprecation

A new OCAPI version is created whenever Digital:

  • Adds a new document property, resource parameter, or resource.
  • Modifies the type of a document property, resource parameter, or resource.
  • Modifies the name of a document property, resource parameter, or resource.
  • Deletes a document property, resource parameter, or resource.

Whenever Digital creates a new OCAPI version, it also deprecates the former OCAPI version. This encourages customers and developers to:

  • Implement new client applications on top of the current OCAPI version.
  • Upgrade existing applications on a regular basis.

Version numbers

Digital constructs OCAPI version numbers by taking the last two digits of the current year ("13" for 2013), adding a period (.), and adding consecutive numbers, starting with 1. For example, "13.1" is the first version of 2013.

Depending on the context, the version number is specified differently:

  • In URLs, the following syntax is used: v<year>_<consecutive number>. For example: "v13_1".
  • In documents, the following syntax is used: <year>.<consecutive number>. For example: "13.1".

Version lifecycle

Version State Support Description
Current Yes The newest version. Always develop new applications using the current version. Commerce Cloud ensures that an OCAPI version is supported for at least two years. During this period Digital ensures the stability and backwards-compatibility of the version enclosed feature set.
Deprecated Yes Digital deprecates an OCAPI version when a new version is published. Support, stability, and backwards-compatibility are ensured for up to two years after the publish date.
Obsolete No Deprecated versions become obsolete automatically two years after being published. Digital deletes obsolete versions without further notice.

Notification process

Digital notifies customers about new and deprecated versions on the XChange portal and in the Digital Release Notes.

Infocenter Retirement: On June 30, 2023, the Infocenter was retired, and documentation currently hosted on the Infocenter will be published to Salesforce Help, Commerce Cloud Developer Center, and Salesforce B2C Commerce Developer Documentation Resources. For more information, see the release note.

X OCAPI versions 15.x and 16.x will be retired on March 31, 2021. For dates and more information, see the OCAPI versioning and deprecation policy and this Knowledge Article.