--- schema_version: "1" id: 4f8aae1fdab8744b422a6728c883b373805539010d1ad9cf2060a6d9164fed79 title: API collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_api.md canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_api.htm&release=262.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: b652317b46bdf76cb2dbdd0b0a3413a7af58cc321af2bd4b80b1b2112a31334a description: Learn about improvements, new capabilities, and important announcements in API version 67.0. products: - Cross Cloud release: "262" --- # API Learn about improvements, new capabilities, and important announcements in API version 67.0. - **[Connect AI Agents to Salesforce Securely with Hosted MCP Servers (General Availability)](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_hosted_mcp_servers_ga.htm&release=262.0.0&type=5)** Connect any MCP-compatible AI client, including Claude, ChatGPT, Cursor, or custom agents, to your Salesforce org using the open Model Context Protocol (MCP) standard. Your AI agents can now interact with Salesforce data and automation in a secure, governed way with standard OAuth authentication. Hosted MCP servers require no infrastructure to manage. Access sObject operations, Data 360 queries, Tableau analytics, and product APIs, and create custom tools using your own Apex actions, flows, and named queries without writing integration code. - **[Enable AI Assistants to More Efficiently Find and Create Salesforce Metadata (Beta)](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_context_mcp_server_beta.htm&release=262.0.0&type=5)** The Salesforce API Context MCP server now has five Metadata API Context MCP tools instead of one. These more granular tools mean that AI agent queries can be targeted, response times are faster, and your token usage can be more efficient. The Metadata API Context MCP tools provide contextual information about Salesforce metadata types to help generate accurate Salesforce metadata files. These tools give you complete field definitions, valid values, constraints, and examples for metadata types. - **[Create Agent Actions from Named Query API (Generally Available)](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_named_query_ga.htm&release=262.0.0&type=5)** Define and expose custom SOQL queries as scalable actions for REST API clients and AI agents by using the Named Query API. A named query can retrieve data quickly and more efficiently than existing Flow or Apex processes. - **[Salesforce Platform API Versions 31.0 Through 40.0 Are Being Retired](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_retirement.htm&release=262.0.0&type=5)** Salesforce Platform API versions 31.0 through 40.0 are being deprecated and retired. - **[Restrict Login Access to SOAP API](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_soap_login.htm&release=262.0.0&type=5)** Enhance security by controlling who can authenticate using SOAP API login() with the new Any API Auth permission. The permission is enforced by default in newly created orgs. You can choose to enable it in existing orgs. - **[Use JWT-based Access Tokens with SOAP API](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_soap_jwt.htm&release=262.0.0&type=5)** SOAP API now supports JWT-based access tokens from Salesforce OAuth flows. This feature provides parity with REST API authentication mechanisms and enables secure token sharing with external services. - **[Query Data 360 More Precisely](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_soql_set_options.htm&release=262.0.0&type=5)** Use the new SET OPTIONS clause in SOQL queries to specify Data 360 dataspaces and control how NULL and empty string values are handled. When querying Data 360 data lake objects, add the clause at the end of your SOQL query to get more precise results. - **[Calculate Values in a SOQL WHERE Clause (Pilot)](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_soql_where.htm&release=262.0.0&type=5)** Perform arithmetic calculations directly in your SOQL WHERE clauses using the new FORMULA() function. Compare values between fields without requiring formula fields or post-processing logic, and make your queries more efficient and expressive. - **[Get Better Visibility into Your Agent's API Usage with Improved Tracking](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_total_usage.htm&release=262.0.0&type=5)** API Total Usage EventLogFiles now distinguish between Apex REST and AuraEnabled Apex calls, making it easier to monitor and analyze your agent's behavior. New entries to the API Total Usage EventLogFiles reflect the updated tracking. - **[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=262.0.0&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 date to Spring ’27. - **[Control Your Salesforce Edge Network Routing with Self-Serve Setup](https://help.salesforce.com/s/articleView?id=release-notes.rn_control_edge_network_routing_with_self_serve.htm&release=262.0.0&type=5)** You can now manage your network routing with self-serve options available on the My Domain Setup page and maintain connection reliability without contacting Salesforce Customer Support each time. - **[Get Notified About Composite API Requests with EventLogFile Event Types](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_composite_em.htm&release=262.0.0&type=5)** Query the EventLogFile object for the CompositeApi and CompositeApiSubrequest event types to get details about composite API and composite graph API requests and subrequests. - **[Other Improvements to Generating an OpenAPI Document for sObjects REST API (Beta)](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_rest_openapi_spec_beta.htm&release=262.0.0&type=5)** With the latest version of the OpenAPI specification, you can query for all available resources and use a wildcard character in URIs. - **[Migrate your Standard Volume Platform Events to High Volume Platform Events](https://help.salesforce.com/s/articleView?id=release-notes.rn_migrate_your_standard_volume_platform_events_to_high_volume_platform_events.htm&release=262.0.0&type=5)** Starting in Winter ‘27, Salesforce no longer supports standard volume platform events. To help you transition your standard volume platform events to high volume platform events, Salesforce has created a migration tool. If you don’t run the migration tool, your standard volume platform events won’t be migrated to high volume platform events. You can use either the Tooling API or the Metadata API to run the migration, which typically takes about 10–15 minutes to complete, but may run for as long as 24 hours in rare situations. Before starting a migration, first ensure that all publish activity has stopped and all subscribers, including triggers and flows, are done processing. While the migration is running, publishes won’t work and you’ll be unable to create new triggers or flows until the migration finishes. You will receive an email once the migration is complete. - **[Use New EventBus.publishWithAccessLevel() Methods for Better Access Control](https://help.salesforce.com/s/articleView?id=release-notes.rn_use_new_eventbus_publishwithaccesslevel_methods_for_better_access_control.htm&release=262.0.0&type=5)** The EventBus class has a new set of publishWithAccessLevel() methods that mimic the existing publish() methods and take a required non-null AccessLevel parameter. These new methods are recommended over the existing publish() methods because they more clearly define the type of access needed by the Apex code. - **[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=262.0.0&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. - **[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_262rn.htm&release=262.0.0&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. - **[login.database.com Is Being Retired](https://help.salesforce.com/s/articleView?id=release-notes.rn_api_login_database_retirement.htm&release=262.0.0&type=5)** Salesforce is retiring login.database.com in June 2026. Update all login.database.com references to login.salesforce.com.