Contact
Privacy
Legal Notice - Impressum
Career
News
The Salesforce Winter '27 release introduces API version 68.0, along with raised Apex governor limits, a new Platform API retirement wave, and tighter SOAP authentication requirements.
Winter '27 is less disruptive than Summer '26 for existing Apex code, but it adds a hard authentication requirement for SOAP API login() and new compiler warnings for Apex classes and triggers on older API versions. Audit permission assignments and legacy Apex versions early.
All users must have the Use Any API Auth user permission to authenticate with the SOAP API login() operation. Users without it can no longer authenticate and will encounter an error. Administrators assign it through profiles or permission sets. This is a live requirement rather than a scheduled retirement, so SOAP integration users should be audited before the org upgrades.
The SOAP API login() call in versions 31.0 through 64.0 will be retired in Summer '27. Applications on these versions will fail with an error indicating the endpoint has been deactivated. Salesforce recommends migrating integrations to External Client Apps and modern OAuth-based authentication before Summer '27. A test run in Setup disables the call so you can identify impacted integrations early.
A second retirement wave covers Platform API versions 21.0 through 30.0, affecting Bulk API, SOAP API, and all REST APIs beneath /services/data/vXX.X/. It runs alongside the announced retirement of versions 31.0 through 40.0. Use the API Total Usage event to identify requests on unsupported versions, and enable the test run in Release Updates to reject those calls ahead of enforcement.
Apex classes and triggers saved at API versions 9.0 through 19.0 will be retired in a future release. The compiler now warns when you compile or deploy at these versions, surfacing in Setup, the Salesforce CLI, VS Code extensions, and the Tooling API. Update affected classes to API version 20.0 or later.
This applies only to Apex class and trigger metadata versions, not Visualforce, Flow, or custom Apex REST and SOAP endpoints, and is separate from the Platform API retirement.
The release update requiring API traffic to use an org's My Domain login URL rather than instance-based endpoints has been postponed a second time, from Spring '26 to Spring '27. Salesforce enforces it in phases.
Enforced in Summer '27, this release update blocks managed package session IDs from authenticating anonymous Apex. Installed packages can no longer call UserInfo.getSessionId() and use the result to run anonymous Apex. Packages with namespaces created in Summer '26 and later are already blocked regardless of subscriber settings.
Winter '27 raises long-standing Apex governor limits and simplifies version management across REST and Streaming APIs.
The Apex heap limit for synchronous transactions increases from 6 MB to 10 MB, and asynchronous from 12 MB to 25 MB, enabled automatically on the Winter '27 schedule. Confirm your org's limits with Limits.getLimitHeapSize(). For teams deploying from Winter '27 sandboxes into Summer '26 production, an Enforce the Summer '26 Apex heap limit setting holds nonproduction orgs at the older limits. See how this plays out in a real batch job scenario.
REST API endpoints now accept latest in place of a numbered API version segment. Requests route to the most recent API version the org supports, with the resolved version returned in the List Available REST API Versions response. Teams pinning API versions deliberately for stability should continue to do so. More on what else changed for developers in Winter '27.
Starting with API version 68.0, the Streaming API server emits a per-channel replay watermark in ext.replay on every successful /meta/connect response. Clients use it to update their replay ID on resubscription without waiting for events to be delivered, allowing clients to resume from a more recent replay position without waiting for additional events. This matters most for high-volume subscribers recovering after a disconnect.
The elastic limits beta now covers Batch jobs alongside future methods and Queueable jobs. When an org exceeds its rolling 24-hour asynchronous job limit, jobs continue to enqueue up to a higher elastic limit rather than failing. Beyond that, the system throttles in-flight Batch processing and restricts new Batch jobs to one at a time.
Bulk API 2.0 adds marketing objects supporting insert and upsert, plus a refresh operation for marketing objects only that replaces all data in the target data set. Marketing object ingestion requires a Marketing Cloud license.
A new Apex Symbol API returns Apex type information via GET to /services/data/vXX.X/tooling/symbols. A second resource, /services/data/vXX.X/tooling/apexCompileResults, retrieves compilation results for invalid classes or triggers so orgs can recompile selectively. The Test Discovery API adds a testLevel query parameter, replacing the deprecated showAllMethods.
Managed package developers can resolve field name conflicts by setting the explicitNamespace property on a Database.QueryOptions object and passing it as a bind variable in the SOQL SET OPTIONS clause. Queries without the clause keep existing behavior.
A beta FORMULA() function performs arithmetic directly in a SOQL WHERE clause, allowing field-to-field comparisons without a formula field or post-processing. It is available in sandbox, Developer Edition, and scratch orgs in API version 68.0 and later, not production.
GraphQL API adds a lookupValues field providing lookup search for Salesforce lookup and relationship fields, supporting type-ahead search, most recently used lookups, and full search. This reduces round trips when populating lookup fields in custom interfaces.
API Catalog centralizes services including APIs and MCP servers in one place. Teams can bring in APIs from MuleSoft, Heroku, and Apex for use in Agentforce agents and flows, activate Salesforce-hosted MCP servers for external clients, and register external MCP servers. This consolidates separate Summer '26 capabilities into one managed surface.
Apex integration tests now support real HTTP callouts, including External Services configured through Named Credentials. In Summer '26 integration test callouts were limited to Agentforce and Data 360. The expanded scope is designed to validate full request-response cycles against external systems in scratch orgs, surfacing serialization mismatches, authentication failures, and timeout behavior that mocked callouts do not cover. A new @BeforeClass annotation sets up shared test data. The ApexIntegrationTests feature must be enabled in the scratch org definition file.
The Marketing Cloud Engagement MCP server adds 40 tools across seven areas: automations and activities, campaigns, bulk and asynchronous data, Content Builder, data extensions, contacts, and tracking. AI assistants can run Automation Studio activities, manage campaigns and folders, upsert bulk data, query rows by external key, erase contacts for GDPR and CCPA requests, and pull email tracking events.
A REST API now manages all content types in the Marketing Cloud Next Content Management System, covering create, modify, and search across Email, SMS, WhatsApp, and Mobile App channels, plus video, content blocks, tracked links, and forms.
Revenue Management again carries a substantial set of Connect REST API changes, concentrated in billing and pricing.
Billing adds three new Connect REST API resources: /revenue/billing/credit-memos/actions/process-refund issues refunds against credit memos, /commerce/invoicing/invoices/collection/actions/checkout creates a unified checkout transaction, and /connect/industries/collection/composite-collection-plan creates collection plans and their items in one request. Salesforce Pricing adds resources for cloning a pricing recipe and retrieving valid pricing elements. Changed Connect REST APIs also cover Product Catalog Management, Product Configurator, and Transaction Management.
Salesforce Contracts introduces resources for starting a risk analysis on a contract document version and retrieving its status and findings, plus playbook resources for matching content chunks against a query and creating a playbook version from a content document.
Group Benefits adds Connect APIs supporting end-to-end group insurance workflows including census, quote, contract, and policy lifecycle management, plus endorsements and renewals. Consumer Sales adds an Amend API via /connect/consumer/initiate-amend.
Manufacturing introduces a Flatten Account Internal Organization Unit Hierarchy API that converts multi-level hierarchy trees into flat records, flattening multi-level organizational hierarchies into a tabular structure for easier reporting and filtering. Brokerage also gains new Connect REST resources.
Use Any API Auth user permission is now required for SOAP API login(). Audit integration user profiles and permission sets before your org upgrades, since users without it can no longer authenticate.latest in place of a numbered version, and Streaming API emits a per-channel replay watermark in ext.replay for faster resubscription syncing.For full details, consult the official Winter '27 Release Notes (API v68.0) on Salesforce Help.
To explore related topics and stay current with Salesforce developments, the following resources provide additional context and practical insight: