Salesforce Summer '25 Release API Updates: What Developers Need to Know About API Version 64.0

‍

Salesforce’s Summer ’25 release (API version 64.0) introduces a wide array of API-level enhancements that further streamline development workflows, improve observability, and enable deeper integrations across clouds. This article highlights the key API updates that developers and integration architects should consider for adoption and compatibility planning.

Breaking Changes and Deprecations

API Version Retirement

Salesforce has officially retired API versions 21.0 through 30.0 across REST, SOAP, Bulk, and Tooling APIs. Integrations using these versions must be upgraded to supported API versions to prevent runtime failures. If you’re still using these legacy versions, review how to migrate from deprecated Salesforce APIs to maintain compatibility.

Use Your Org’s My Domain Login URL for API Access

To support enhanced domain-based routing, Salesforce now requires all API calls to use the org-specific My Domain URL. This helps maintain consistency across Hyperforce environments and reduces risks related to instance migration.

Outbound Message Timeout Reduced

The timeout for Outbound Messages has been reduced from 60 seconds to 20 seconds, improving resource management and ensuring faster error handling in asynchronous integrations. Teams using legacy or high-latency endpoints should verify their ability to process within the new threshold.

Salesforce Functions Retirement

Salesforce Functions is now officially retired and unavailable for new purchases or renewals. Teams looking for a Salesforce Functions alternative in 2025 should consider using Apex + Async APIs or leveraging external serverless functions via Event Relay.

Platform API Enhancements

OpenAPI Specification for sObjects REST API (Beta)

Salesforce now supports OpenAPI specifications for the sObjects REST API resource. Developers can generate client SDKs, visualize request/response structures, and use wildcard URIs to explore metadata dynamically. This enhancement introduces OpenAPI support in Salesforce REST API, enabling auto-generated documentation and Swagger-based tooling.

Streaming API: Disconnect Event Notifications

A new /meta/disconnect channel has been introduced to notify subscribers when a disconnection occurs. This improves resiliency in streaming architectures by enabling clients to detect dropped connections and re-establish sessions more efficiently. Developers can now implement a Salesforce Streaming API disconnect handling example to improve resiliency in their event-driven integrations.

Composite API Monitoring

Two new event types – CompositeApi and CompositeApiSubrequest – are available through the Event Monitoring system. These events offer fine-grained visibility into composite request behavior for diagnostics and performance auditing.

Metadata API and Tooling Enhancements

• rootTypesWithDependencies parameter: New metadata deployment behavior that reduces dependency issues by pulling in all related types.

• Pilot Metadata Types: Can now be retrieved and deployed in API version 64.0, allowing early access and testing with selected features.

• Metadata Coverage Report Redesign: The legacy coverage tool/report is deprecated and replaced with a more interactive experience for checking deployment readiness

• Pub/Sub API in Hyperforce: Now generally available across all Hyperforce regions, supporting real-time architectures at global scale.

Sales Cloud API Updates

Agentforce Enhancements

Salesforce expanded Agentforce capabilities to support multilingual outreach via Agentforce SDR, test email generation, and sales process adherence via Agentforce Deal Agent. These APIs allow tighter automation integration with Sales Cloud records.

LinkedIn Lead Sync API Deprecation

The native integration with LinkedIn Lead Sync is being deprecated. LinkedIn deprecated its legacy lead sync API effective late 2024. To continue syncing leads in Salesforce Summer ’25, admins must enable the ‘LinkedIn Lead Gen’ API connection setting (Setup > LinkedIn Lead Gen). Organizations must update their sync strategies to avoid disruptions in lead capture workflows.

Data Cloud API Features

Direct-DMO and Copy Field Enrichments

New APIs allow for enriched related lists and data population on objects such as cases, contracts, and products, helping extend CRM profiles with unified data.

Deployment of Enrichments from Sandbox to CRM

Data Cloud enrichments created in sandbox environments can now be promoted to CRM production environments using deployment APIs, enhancing support for release pipelines and CI/CD.

Event Relay Now Packageable

Configurations for Event Relay can now be included in managed packages (1GP, 2GP, unlocked), allowing ISVs and enterprise teams to distribute pre-configured real-time event forwarding to external platforms (e.g., AWS, Azure).

Industry Cloud API Enhancements

Industry-specific features continue to be expanded, with metadata and API support for Omnistudio, Context Service, and Asset Management in sectors like Manufacturing, Public Sector, and Health Cloud. While no new HL7 FHIR or ERP connector APIs were introduced in Summer ’25, Industry Clouds benefit from enhanced OmniStudio, Context Service, and Asset Management API support as well as Data Cloud Related List Enrichments and operational automation.

Service Cloud API Updates

Field Service APIs now offer enhanced capabilities for data capture (PDF, NPS, structured forms) and route conflict handling. Though Omni-Channel routing APIs weren’t updated in this release, the general focus remains on supporting intelligent scheduling and mobile agent workflows.

Final Thoughts

Following the Winter '25 and Spring '25 releases, Salesforce’s Summer '25 release concludes the API updates for 2025. Across these releases, Salesforce advanced integration performance, real-time streaming capabilities, and metadata deployment flexibility for modern, scalable architectures.

With Summer '25 release, Salesforce deepens its commitment to scalable, observable, and developer-friendly APIs. From outbound message performance improvements to modernized metadata tooling and enhanced TypeScript compatibility, this release prepares the platform for increasingly modular and event-driven architectures. Developers should review version usage and leverage the new capabilities in API version 64.0 for forward compatible and efficient integration.

For more details, refer to the Official Summer ’25 Release Notes (API v64.0) on Salesforce Help.