---
schema_version: "1"
id: 08f20181ca08f140ade708098d0c4087aabcfa00870332bf3e0c941a684d54e8
title: Update Instanced URLs in API Traffic (Release Update)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_update_instanced_urls_in_api_traffic.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_update_instanced_urls_in_api_traffic.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4d1f38974f88c82bf79a4b41e9ef05c7d7bceb7a339064c0a8e950d5af13f532
description: 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.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Update Instanced URLs in API Traffic (Release Update)

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.

**Where:** This change applies to Lightning Experience and Salesforce Classic in all editions except Database.com.

**When:** Salesforce enforces this update on a rolling basis shortly after Winter ’27 deployment. For specific enforcement dates, see [End-of-Support Schedule for Incorrect Instanced URLs in API Traffic](https://help.salesforce.com/s/articleView?id=005228941&type=1&language=en_US).

If you enable this change before the related known issue is resolved, SOAP login URLs via Visualforce pages can return a 400 Bad Request error. Salesforce plans to deploy a fix for that issue June 16–18, 2026, so we recommend that you test this change after June 18, 2026.

**Why:** Salesforce is decommissioning the service that supports hard-coded references to an incorrect instance name in API application traffic routing. This approach helps make sure that integrations continue to function smoothly while improving security, because My Domain URLs are unique to each org.

**How:** Replace instanced URLs in your API calls with your My Domain login URL.

Test this change after June 18, 2026. From Setup, in the Quick Find box, enter My Domain, and then select **My Domain**. Under Redirections, enable **Block API traffic that uses an incorrect instanced URL**. If you enable this change before June 19, 2026, SOAP login URLs via Visualforce pages can return a 400 Bad Request error.

To review this update, from Setup, in the Quick Find box, enter Release Updates, and then select **Release Updates**. For Update Instanced URLs in API Traffic, follow the testing and activation steps.

#### See Also

- [_Knowledge Article_: End-of-Support Schedule for Incorrect Instanced URLs in API Traffic](https://help.salesforce.com/s/articleView?id=005228941&type=1&language=en_US)
- [Release Updates](https://help.salesforce.com/s/articleView?id=release-notes.rn_ru.htm&release=260&type=5 "Salesforce periodically provides release updates that improve the performance, logic, security, and usability of our products. The Release Updates page provides a list of updates that can be necessary for your organization to enable. Some release updates affect existing customizations.")