Salesforce Spring '25 Release API Updates: What Developers Need to Know About API Version 63.0

‍

Salesforce Spring '25 API Version 63.0 introduces significant updates for developers, including API deprecations, new integration capabilities, performance enhancements, and governance improvements. This overview highlights the most impactful changes across Salesforce’s API landscape to help developers optimize their integration workflows and stay ahead of upcoming deprecations.

Breaking Changes and Deprecations

Salesforce API Versions 21.0 to 30.0 Retirement

Salesforce is officially retiring API versions 21.0 through 30.0 in Summer '25. Developers must migrate integrations to newer versions to ensure continued functionality and avoid service disruptions. Any legacy integrations still using these versions should be updated to API Version 63.0 or later. Learn More

Instance-Based Domain Names Discontinuation

Salesforce is deprecating instance-based domain URLs (e.g., na1.salesforce.com). All API requests must use My Domain URLs instead. Developers should update hardcoded instance-based URLs in Apex code and integrations. The best practice is to use Url.getOrgDomainUrl() to retrieve the appropriate domain dynamically. Learn more

Platform API Highlights

Bulk API 2.0 Platform Events (Beta)

Developers can now subscribe to platform events that notify them of Bulk API V2 job progress. This eliminates the need for polling API requests, reducing unnecessary API consumption and improving efficiency. The new BulkApi2JobEvent event type provides real-time status updates on query job completion. Learn more

Improved Event Relay Packaging

Event Relay, which enables event streaming to external systems (e.g., AWS, Azure), is now packageable within Second-Generation Managed Packages (2GP), unlocked packages, and first-generation managed packages. This allows ISVs and enterprise developers to distribute event relay configurations as part of packaged solutions via AppExchange.

Increased Limit for Long-Running Apex Requests

• Salesforce has modified the long-running synchronous Apex transaction limit, which now scales based on the number of licenses in an org.  
• Previously, organizations were limited to 10 concurrent requests exceeding five seconds. With Spring '25, this limit is now dynamically adjusted based on the number of Salesforce user licenses, allowing up to 50 concurrent long-running requests for larger enterprises.
• This change enables businesses with high transaction volumes to execute more complex operations without encountering governor limits, reducing bottlenecks for high-volume API calls and background processing.

Data Cloud API Features

Data Cloud Event Streaming Enhancements

• Salesforce has introduced improvements in Data Cloud event streaming, allowing for more efficient real-time data synchronization between Salesforce and external data sources.
• With the expanded REST API support, developers can now subscribe to custom event triggers that capture data changes more accurately. Additionally, JDBC driver support has been enhanced, enabling seamless API integration with external analytics tools, databases, and enterprise applications.
• This upgrade makes Data Cloud APIs more robust for enterprises looking to leverage Customer 360 data dynamically across platforms.

Industry Cloud API Updates

New Industry-Specific API Enhancements

• Salesforce continues to expand industry-focused API capabilities, making it easier for developers to integrate sector-specific solutions. The Spring '25 update introduces enhanced Financial Services Cloud APIs, which now offer improved API-based transaction tracking and automated compliance checks.  
• Similarly, Healthcare and Life Sciences Cloud now supports FHIR-based API integration, streamlining the exchange of health records with electronic medical record (EMR) systems.
• Manufacturing Cloud has introduced supply chain visibility APIs, enabling manufacturers to connect Salesforce with inventory management and logistics platforms more effectively.

Service Cloud API Updates

Enhanced API Capabilities for Omni-Channel Routing

• Service Cloud now supports API-driven Omni-Channel routing enhancements, allowing developers to better control and automate work distribution to customer support agents based on real-time metrics.  
• The Omni-Channel Routing API has been expanded to allow for custom prioritization rules, integrating with third-party AI models to assess urgency, customer sentiment, and support tier levels.  
• This enables businesses to build smarter case assignment logic through API workflows and external AI-powered engines, improving response times and customer satisfaction scores.

Marketing Cloud API Updates

Improved Personalization APIs

• Marketing Cloud introduces new API capabilities for content personalization and automation, enhancing marketers' ability to deliver tailored experiences to customers across different channels.  
• The Personalization API now allows developers to retrieve and apply AI-driven recommendations dynamically, improving content delivery for email campaigns, SMS, and web interactions.  
• Enhanced customer engagement tracking APIs provide real-time behavioral insights, allowing organizations to adjust marketing automation flows dynamically based on audience engagement data.

Looking Ahead

Spring '25 brings substantial API enhancements, particularly in security, automation, and integration performance. Developers should proactively take steps to migrate deprecated APIs, adopt new authentication mechanisms, and leverage the latest Salesforce tools for optimization.

For more details, refer to the Official Salesforce Spring '25 Release Notes and the Salesforce Developer’s Guide to the Spring ‘25 Release. Additionally, you can download the PDF version of the Salesforce Spring '25 Release Notes.