Spring 20 Changes to API Limits in Salesforce

As Salesforce becomes more embedded in organisations and we see increased cross cloud integration between Salesforce products (E.g. Commerce <-> Service, Marketing <-> Service etc) there has been increased API consumption for integration at customers. The existing API limits which have been in place for a considerable period of time were becoming a source of friction for customers and have been increased significantly in the latest Spring 20 Release.

Spring 20 Release has brought some good changes to API limits. From the release notes:

• The default daily API request allocation has been raised from 15,000 to 100,000 (this is the minimum, before any add ons that might purchased);
• The maximum daily cap of 1,000,000 API requests has been removed;
• Your org can now exceed its API daily request limit without being blocked (subject to system health). A generous hard cap is in place to safeguard platform resources. A new usage-based entitlement shows the total number of API requests aggregated over 30 days.

Release Notes

It’s still always worth considering API traffic optimisation when building your integrations

• Evaluate real-time integration VS scheduled jobs.
• Evaluate Synchronous VS Asynchronous integrations.
• Use the REST API Composite Resources to execute multiple API requests in a single call.
• Evaluate alternatives to the REST API for inbound communication in Sales Cloud. For example Platform Events or Bulk API

Let me know in the comments if you have other recommendations for API traffic optimisation.