Salesforce Platform API Versions 21.0 through 30.0 Retirement

Overview

Natterbox has a process to constantly review versions of Salesforce SOAP and Rest APIs that are used within the platform to ensure that no applications use versions that Salesforce has scheduled to retire.  

This process has been followed for the affected API versions from the Salesforce Summer ‘22 release and all changes have been implemented to allow continuation of the current service. 

The Natterbox App within Salesforce will not be affected by this retirement and there will be no impact to Natterbox services. No action or upgrade is needed by customers for these changes to take effect.

Information

With the Summer '22 release, the following Salesforce Platform API legacy versions will be deprecated and no longer supported by Salesforce:

SOAP: 21.0, 22.0, 23.0, 24.0, 25.0, 26.0, 27.0, 28.0, 29.0, 30.0

REST: v21.0, v22.0, v23.0, v24.0, v25.0, v26.0, v27.0, v28.0, v29.0, v30.0

Bulk: 21.0, 22.0, 23.0, 24.0, 25.0, 26.0, 27.0, 28.0, 29.0, 30.0

Customers can continue to access these legacy API versions until Summer '23 is released, which is when these legacy versions will become retired and unavailable.

When versions 21.0 through 30.0 are retired, applications consuming these versions of the API will experience disruption as API calls will fail and result in an error indicating that the requested endpoint is not found and unable to be processed by the platform.

More information on the API retirement can be found here.

FAQ

What is Platform API?

Salesforce APIs are a way for other applications (or code in other applications) to programmatically access data within your Salesforce org, in a simple and secure manner.

Why are there different API versions?

Every time Salesforce releases a new application version, its API version is updated as well. It tells the version of the developed code. API versioning plays an important role while developing code for an application. 

Why are API Versions 30.0 and below listed against the Natterbox Namespaces in the Salesforce Apex Classes List page?

Apex classes have a different version of APIs than the ones due to be retired, Apex classes get their version when they are originally developed. There is no need to update the version and release unless the functionality supplied by Salesforce in a more recent release is used in the class.

Will Natterbox’s API Versions 30.0 and below in apex class be affected after Summer ‘22 release?

No, as mentioned in the Salesforce article,
“This retirement cases.does not impact the following:

    -Custom Apex REST & SOAP Web Services, Apex Classes, or Apex Triggers
    -Versioned metadata components in a managed package”

When are Natterbox adding support for new functionality available in later API versions?

Natterbox Product team regularly reviews the new functionality available in the latest version of the Salesforce API to understand which needs to be integrated within the Product.  All changes are added to the backlog of work, prioritised and planned into the Product and Technology Roadmap. You can keep up to date with the latest improvements to the Natterbox platform at our release notes page.