Contact
Privacy
Legal Notice - Impressum
Career
News
The Salesforce Spring ’26 release API version 66.0 introduces several changes that directly affect existing integrations and custom development relying on Salesforce APIs.
These updates primarily focus on security hardening, consistency of API behavior, and the gradual retirement of legacy patterns. Integration teams should review these changes carefully, as some may require endpoint updates, authentication adjustments, or code refactoring.
Salesforce has ended automatic redirections for legacy and instance-specific hostnames used in API requests. Integrations that previously relied on redirected endpoints such as instance-based URLs or deprecated hostnames must now explicitly use supported endpoints, including My Domain URLs or standard login endpoints.
This change affects all major Salesforce APIs, including REST, SOAP, Bulk, and Metadata APIs. API clients that continue to use unsupported hostnames may encounter request failures once redirections are fully removed.
In Spring ’26, Salesforce changes the default behavior for Connected App creation. Previously, Salesforce orgs allowed connected apps to be created automatically by default. With this release, that default setting is turned off.
As a result, control over which applications can connect to a Salesforce org becomes more restrictive, reducing the risk of unauthorized or unintended integrations. Administrators must now explicitly enable connected app creation if it is required, adding an additional layer of security and governance.
Existing connected apps continue to function without interruption. However, Salesforce recommends using the External Client App feature going forward, including new integrations and migrating existing applications. This approach provides a more secure and centralized way to manage authentication and access for applications connecting to Salesforce.
Salesforce introduces a release update that changes how sharing recalculations are performed after large-scale updates to groups or roles. To improve performance in these scenarios, Salesforce now performs sharing recalculations asynchronously rather than immediately.
This change can affect custom Apex code or Flows that assume synchronous sharing behavior following updates to groups or role hierarchies, particularly logic that depends on predictable recalculation timing or directly queries sharing-related data.
Developers should review and test automation that relies on immediate sharing outcomes after modifying groups or roles to determine whether adjustments are required under the new asynchronous sharing recalculation behavior.
<apex:inputField> Elements to Prevent XSS As part of ongoing security improvements, Salesforce now escapes the label attribute of <apex:inputField> elements by default to prevent cross-site scripting (XSS) vulnerabilities. While this change primarily affects Visualforce rendering, it can impact API-adjacent use cases where Visualforce pages are embedded in integration flows or exposed through custom endpoints.
The Salesforce Spring ’26 release introduces several enhancements at the platform API level that improve scalability, flexibility, and integration extensibility. These updates primarily affect Apex-based integrations, custom REST implementations, and API consumers that rely on large data volumes or dynamic metadata access.
Spring ’26 introduces API version 66.0, which becomes the latest available version across Salesforce platform APIs. As with prior releases, existing integrations continue to function without modification when pinned to older API versions. New platform capabilities and behavioral changes are exposed only when explicitly adopting version 66.0.
Testing against the new version is recommended to identify any subtle behavioral differences, especially where Apex execution, metadata handling, or security enforcement is involved.
Apex cursors are now generally available, providing a new mechanism for processing large SOQL query results incrementally rather than loading entire result sets into memory at once.
This enhancement is particularly relevant for API-driven batch jobs, data synchronization processes, and integrations that operate on high-volume datasets. This change improves the reliability and scalability of custom APIs and backend services built on Apex when handling enterprise-scale data volumes.
Salesforce now allows Apex REST endpoints and @AuraEnabled controller methods to be exposed as Agent actions. While Agentforce itself is a broader platform capability, this update is relevant from an API perspective because it enables existing custom APIs to be invoked programmatically by agent-driven processes without duplicating logic.
From an integration standpoint, it encourages clearer separation between API logic and orchestration while maintaining a single source of truth for business logic exposed through Apex.
Spring ’26 introduces new Apex functionality that enables programmatic extraction of picklist values scoped to specific record types. This addresses a long-standing challenge for API consumers and custom integrations that need to dynamically align with Salesforce metadata constraints.
For external systems, middleware, or custom front-end applications that rely on Salesforce APIs, this enhancement simplifies validation logic and reduces the need for hardcoded picklist mappings. By allowing integrations to retrieve context-aware picklist values directly through Apex, developers can build more resilient and metadata-driven API solutions.
The Salesforce Spring ’26 release continues to expand Data Cloud’s role as a centralized data platform by introducing API-relevant enhancements focused on analytics integration, query performance, and secure external connectivity. These updates primarily affect organizations using Data Cloud as part of their data ingestion, analytics, and activation architectures.
CRM Analytics datasets are now generally available for use directly within Data Cloud. This change allows analytics datasets to be consumed alongside other Data Cloud data sources, reducing the need for separate data duplication or complex synchronization logic.
Integrations that previously accessed CRM Analytics data independently can now align more closely with Data Cloud ingestion, transformation, and activation workflows, enabling more consistent data access patterns across APIs.
Spring ’26 introduces Data Cloud SQL as a beta capability, providing more advanced SQL-based querying over Data Cloud datasets. This feature is designed to support complex analytical queries and improve performance when working with large-scale data volumes.
While still in beta, this capability signals a shift toward more flexible, query-centric access patterns for Data Cloud data through APIs and analytics integrations.
In Spring ’26, Snapshot Data Recipes support optimized upsert and delete operations when a primary key is defined. These optimizations improve performance by applying incremental changes rather than reprocessing entire datasets, making dƒata modification more efficient for integrations that update or remove existing records as part of their data ingestion workflows.
Salesforce has expanded support for OAuth-secured external data connections, including Microsoft Azure SQL and private Amazon Redshift instances. These enhancements strengthen authentication and authorization controls for external data sources accessed by CRM Analytics and Data Cloud.
This change improves security posture for data ingestion workflows by eliminating reliance on static credentials and enabling token-based access. Integrations that connect external databases to Data Cloud an now align more closely with enterprise security standards while maintaining programmatic access to external datasets.
In the Salesforce Spring ’26 release, Industry Cloud updates introduce incremental but meaningful improvements to APIs used for data transformation and orchestration within industry-specific solutions. These changes primarily affect OmniStudio-based integrations and custom API workflows that support vertical use cases.
Spring ’26 enhances OmniStudio Data Mapper APIs, including the introduction of additional filtering capabilities such as null-handling operators. These enhancements improve how data is transformed and prepared when moving between external systems and Salesforce Industry Cloud data models.
These updates reduce the need for custom preprocessing logic outside Salesforce by allowing more sophisticated filtering and transformation rules to be applied directly within OmniStudio-driven API workflows. This is particularly relevant for Industry Cloud implementations that rely on complex, file-based, or legacy data sources where incomplete or sparsely populated fields are common.
In the Salesforce Spring ’26 release, Industry Cloud APIs, including OmniStudio APIs, remain unchanged and fully supported. The Spring ’26 documentation references Agentforce features alongside existing APIs, including Apex-based actions that can be reused across automation and orchestration scenarios.
These references indicate that existing Industry Cloud APIs can continue to be used in environments where Agentforce-enabled workflows are present.
Marketing Cloud updates in the Spring ’26 release focus on analytics depth and data accessibility. While no new standalone APIs are introduced, enhancements to underlying platforms affect how marketing data can be accessed and consumed programmatically.
Spring ’26 introduces improvements to Marketing Cloud Intelligence, including enhanced analytics, reporting, and accessibility features. These enhancements are reflected in the underlying APIs that expose marketing performance data, enabling richer and more detailed programmatic access.
Salesforce deepens Tableau integration within Marketing Cloud applications, making more marketing insights available through analytics APIs. This integration supports scenarios where marketing performance data is embedded into external applications or consumed by downstream analytics platforms.
The Salesforce Spring ’26 release has a clear emphasis on security, scalability, and consistency across integration patterns. While most APIs remain backward compatible, several changes such as stricter endpoint usage, connected app governance, and enhancements to Apex and Data Cloud APIs require attention from integration and development teams.
Organizations maintaining long-lived integrations should review the documented release updates carefully, test against API version 66.0 where applicable, and validate that provisioning, authentication, and data-processing logic align with the latest platform behavior.
👉 Read the full Salesforce Spring ’26 Release Notes from the official Salesforce documentation to confirm applicability for your org and integrations.
To explore related topics and stay current with Salesforce developments, the following resources will provide additional context and practical insight: