--- title: Impacts of endpoint deprecation slug: o74e0418 canonical_url: https://docs.coveo.com/en/o74e0418/ collection: coveo-for-salesforce source_format: adoc --- # Impacts of endpoint deprecation Beginning June 3, 2025, Coveo will take the following actions: * Deprecate the Coveo V1 platform (`cloudplatform.coveo.com`) and usage analytics (`usageanalytics.coveo.com`) endpoints. * Block analytics-logging calls made towards search (`+search.cloud.coveo.com/**+`) and administration (`+platform.cloud.coveo.com/**+`) endpoints (and the regional variants). * Block search requests made to the analytics logging endpoints (`.analytics.org.coveo.com/*` and `analytics.cloud.coveo.com`). * Report all analytics-logging calls made to the platform endpoint (`platform.cloud.coveo.com`) as deprecated endpoint usage. See [Endpoint deprecation and other endpoint-related changes](https://docs.coveo.com/en/o1ih0284/) and [Detailed endpoint-related changes](https://docs.coveo.com/en/p59e8291/) for more information. To ensure that your Coveo for Salesforce implementation continues to function as expected, follow the guidelines outlined in this article. ## Version 5.8 and later If you're using [organization endpoints](https://docs.coveo.com/en/mcc80216/), no action is required. If you're not using organization endpoints, API calls won't be blocked but will be flagged under [**Traffic**](https://platform.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/settings/organization/traffic)) in the [Coveo Administration Console](https://docs.coveo.com/en/183/). To ensure optimal performance, [enable organization endpoints](https://docs.coveo.com/en/1275#using-the-advanced-configuration-page). This will improve separation of concerns, resiliency, and make multi-region and data residency deployments smoother. ## Versions 5.2 to 5.7 If you're using [organization endpoints](https://docs.coveo.com/en/mcc80216/), no action is required. If you're not using organization endpoints, you must update to [version 5.8](https://docs.coveo.com/en/n5bj0150#june-2024-release-v5-8-minor-release) to use the analytics endpoint (`analytics.cloud.coveo.com`) instead of the platform endpoint (`platform.cloud.coveo.com`) to send [Coveo Analytics events](https://docs.coveo.com/en/260/). While your API calls will be flagged under [**Traffic**](https://platform.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/settings/organization/traffic)) in the [Coveo Administration Console](https://docs.coveo.com/en/183/), they won't be blocked. To ensure optimal performance, [enable organization endpoints](https://docs.coveo.com/en/1275#using-the-advanced-configuration-page). This will improve separation of concerns, resiliency, and make multi-region and data residency deployments smoother. ## Versions 4.21 to 4.33.1 No immediate action is required. However, upgrading to the [latest v4 release](https://docs.coveo.com/en/3236#july-2023-release-v4-33-1-maintenance-release) is recommended. > **Warning** > > The only exception is if you're using the [Coveo Page View Tracker](https://docs.coveo.com/en/p7b79531/) component. > In this case, you must [upgrade to version 5](https://docs.coveo.com/en/n4680498/) to ensure that the correct analytics endpoint is used. These versions use the platform endpoint (`platform.cloud.coveo.com`) for search requests and the analytics endpoint (`analytics.cloud.coveo.com`) for [Coveo Analytics](https://docs.coveo.com/en/182/). While your API calls will be flagged under [**Traffic**](https://platform.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/settings/organization/traffic)) in the [Coveo Administration Console](https://docs.coveo.com/en/183/), they won't be blocked. For optimal performance, [upgrade to version 5](https://docs.coveo.com/en/n4680498/) and [enable organization endpoints](https://docs.coveo.com/en/1275#using-the-advanced-configuration-page). This will improve separation of concerns, resiliency, and make multi-region and data residency deployments smoother. ## Versions 4.20 and earlier A minimum upgrade to [v4.21](https://docs.coveo.com/en/3236#november-2021-release-v4-21-minor-release) is required. However, upgrading to the [latest v4 release](https://docs.coveo.com/en/3236#july-2023-release-v4-33-1-maintenance-release) is recommended. After upgrading, follow the guidelines in [Versions 4.21 to 4.33.1](#version4guidelines). ## Verify endpoint routing . Review the endpoints used in your organization settings under [**Traffic**](https://platform.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/settings/organization/traffic) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/settings/organization/traffic)). Alternatively, you can access the **Network** tab in your browser's developer tools. . Validate the following endpoints: .. Ensure search requests (`/rest/search`) are being sent to `.org.coveo.com/rest/search` (ideal) or `platform.cloud.coveo.com/rest/search`. .. Ensure analytics requests (`/analytics`) are being sent to `.analytics.org.coveo.com` (ideal) or `analytics.cloud.coveo.com`.