Learn MOAR with Summer ’21: API Version Retirement :

Learn MOAR with Summer ’21: API Version Retirement
by:
blow post content copied from  Salesforce Developers Blog
click here to view original post

Follow and complete a Learn MOAR Summer ’21 trailmix for Admins or Developers by July 31 to earn a special community badge and enter for a chance to win one of five $200 USD Salesforce Certification vouchers. Learn how to participate and review the Official Rules by visiting the Trailhead Quests page.

Salesforce releases new API features and functionality with each major release, and each major release results in a new version SOAP, REST, and Bulk APIs. We are currently at 52 versions of our APIs. But this continued innovation means that we are regularly retiring our older API versions. In the Summer ‘21 release, we will be retiring Salesforce Platform API legacy versions 7.0 – 20.0 of our SOAP, REST and Bulk APIs. These API retirements mean that we can focusing our development efforts on enhancing the latest API versions to improve the overall Salesforce experience when building custom functionality via applications.

Here’s a list of the versions that will be retired:

• 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

As retirement process begins, we are committed to a smooth transition for any customers using these legacy API versions. First, let’s talk about who will be affected by this change. All API-enabled org editions using Salesforce Classic and Lightning Experience will be impacted. But they will be able to continue using those API versions until Summer’22, at which time API versions 7.0 to 20.0 will be retired and unavailable.

So, how should customers prepare for these retirements? Before the Summer ’22 release, you must modify or upgrade your applications to function with current API versions. We know that this will take some work, but moving to newer versions of our APIs will offer advanced capabilities with improved security and performance.

As part of our commitment to API management, we are also releasing an API Total Usage event type in the EventLogFile object.

This event type helps you gain visibility into API version use and streamline your API version management strategy and plans. You can also use it to monitor your general API consumption. This event records calls to SOAP, Bulk v1, and REST API requests up to version 30.0. Data is retained for 24 hours.

If you’re interested in using this new event type, this change applies to Enterprise, Performance, Unlimited, and Developer editions. It will be available in the API but not in the Event Monitoring Analytics app.

What makes this announcement even better? The API Total Usage Event is free to all customers. Customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions can use the EventLogFile to monitor events.

For more information, see the Knowledge Article Salesforce Platform API Versions 7.0 through 20.0 Retirement and the “Salesforce Platform API Versions 7.0 through 20.0 Retirement” release update notice. (From Setup, in the Quick Find box, enter Release Updates.) To learn moar about the API Total Usage Event for EventLogFile, check out the Summer ’21 release notes.

The post Learn MOAR with Summer ’21: API Version Retirement appeared first on Salesforce Developers Blog.

May 19, 2021 at 09:45PM
Click here for more details...

=============================
The original post is available in Salesforce Developers Blog by
this post has been published as it is through automation. Automation script brings all the top bloggers post under a single umbrella.
The purpose of this blog, Follow the top Salesforce bloggers and collect all blogs in a single place through automation.
============================