---
schema_version: "1"
id: 55b459dde19c4d7ffdda0695dcae88afe45d16c238bf34bd225421f0f7578f39
title: API
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_api.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_api.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 36fa3b5e840577387086ed56f38c5160e38bbe633e2b3194f2becdbdb72849f5
description: Learn about improvements, new capabilities, and important announcements in API version 66.0.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# API

Learn about improvements, new capabilities, and important announcements in API version 66.0.

- **[Expose Custom SOQL in REST API Calls Using Named Query API (General Availability)](https://help.salesforce.com/s/articleView?id=release-notes.rn_rest_api_named_query.htm&release=260&type=5)**  
    Use Named Query API to define and expose custom SOQL queries, or Named Query APIs, as scalable actions for REST API clients. Named Query APIs can retrieve data quickly and more efficiently than existing Flow or Apex processes.
- **[Update Instanced URLs in API Traffic (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_update_instanced_urls_in_api_traffic.htm&release=260&type=5)**  
    To prevent disruption when Salesforce ends support for API traffic that uses an incorrect instanced URL, make sure that API traffic to your org uses the org’s My Domain login URL. First available in Summer ’25, this release update was scheduled to be enforced in Spring ’26, but we postponed the enforcement to Winter ’27.
- **[EventBusSubscriber Object’s Position and Tip Fields Are Being Deprecated](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_eventbussubscriber.htm&release=260&type=5)**  
    The EventBusSubscriber object’s Position and Tip fields are being deprecated. They are being replaced with the new fields LastProcessed and LastPublished. The field type is changing from int to string in order to handle large replay IDs. We recommend updating your code to use LastProcessed and LastPublished to avoid issues when the replay ID exceeds the maximum integer size.
- **[Sending Session IDs in Outbound Messages Is Being Removed](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_session_id_outbound_messages.htm&release=260&type=5)**  
    To align with modern security best practices, you can no longer send session IDs in outbound messages starting February 23, 2026. Instead, use OAuth to authenticate. When this change goes into effect, the new outbound message form won't include the option to send a session ID, the IncludeSessionId flag in the API will be ignored and set to FALSE, and the <sessionID></sessionID> element of an outbound message payload won't include a session ID.
- **[Metadata Deployments and Retrievals Have New Limits](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_meta_limits.htm&release=260&type=5)**  
    To maintain predictable performance, we're now applying limits to the volume of metadata deployed and retrieved for four specific metadata types: AIAuthoringBundle, AnalyticsDashboard, AnalyticsWorkspace, and AnalyticsVisualization. These limits restrict the number of metadata components allowed within a single package zip file, and the total number of deployments or retrievals permitted within a 24-hour period.
- **[Data 360 SOQL Query Results Are Limited to 12-MB at a Time](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_data_360_soql_12mb_limit.htm&release=260&type=5)**  
    To prevent large queries from crashing the app server, Data 360 limits Salesforce Object Query Language (SOQL) results to 12-MB. SOQL returns the results up to the size limit with a query more link to paginate through the rest of the results. If a single query result exceeds the size limit, SOQL rejects the query and you can’t retrieve the results.
- **[SOAP API login() Call in SOAP API Versions 31.0 Through 64.0 Is Being Retired (Release Update)](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_upcoming_retirement_260rn.htm&release=260&type=5)**  
    In Summer ‘27, the SOAP API `login()` call in SOAP API versions 31.0 through 64.0 will no longer be supported and no longer be available.
- **[Calls to Invocable Actions Are Validated for Constructor Visibility Requirements in API Version 66.0 and Later](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_rest_constructor_visibility_invocable_action_parameters_v66.htm&release=260&type=5)**  
    Starting in API version 66.0, REST API calls validate that custom Apex classes used as invocable action parameters have visible no-argument constructors. If the constructor isn't visible with appropriate access modifiers, the API call fails. This versioned change applies to Salesforce if you haven't enabled the Enforcing No-Argument Constructor release update. Previously, API calls succeeded even if the constructor wasn't visible. In API version 66.0 and later, the API call fails if the constructor lacks appropriate access modifiers.