--- title: Endpoint deprecation and other endpoint-related changes slug: o1ih0284 canonical_url: https://docs.coveo.com/en/o1ih0284/ collection: manage-an-organization source_format: adoc --- # Endpoint deprecation and other endpoint-related changes Coveo initially went live into the cloud in 2015. Since then, technology and practices have evolved greatly. As a result, to simplify the use and future development of its platform while still providing the same world-class service, Coveo will make the following changes: [%header,cols="~,~"] |=== |Date |Enforced changes |June 3, 2025 |Coveo will enforce [all endpoint changes](https://docs.coveo.com/en/p59e8291/) in non-production organizations and production organizations whose [traffic is already 100% compliant](#do-these-changes-impact-my-organization). |October 1, 2025 |Coveo will block all analytics traffic made towards search (`+search.cloud.coveo.com/**+`) and administration (`+platform.cloud.coveo.com/**+`) endpoints (and their regional variants) for all organizations. See [Change 1](https://docs.coveo.com/en/p59e8291#change-1-block-analytics-logging-requests-made-towards-search-and-administration-endpoints) for details. |December 1, 2025 |Coveo will enforce [all endpoint changes](https://docs.coveo.com/en/p59e8291/) for all remaining production organizations. |=== The [Push API](https://docs.coveo.com/en/78/) endpoint, `api.cloud.coveo.com/push`, is not impacted by these changes. To check [whether your organization traffic is compliant with Coveo's standards](#do-these-changes-impact-my-organization), see the [**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)) panel. If your traffic isn't fully compliant, the panel shows the ratio of requests that will be blocked once the changes are enforced. For a full list of the changes to come, see [Detailed endpoint-related changes](https://docs.coveo.com/en/p59e8291/). For details on the Coveo endpoints, see [Deployment regions and strategies](https://docs.coveo.com/en/2976/) and [Organization endpoints](https://docs.coveo.com/en/mcc80216/). ## Benefits These changes will: * **Prevent hidden breakage for end users.** Ad blockers often target `*.coveo.com`, which can unintentionally block more than just analytics traffic. This may impact search, page load performance, and static asset delivery, silently breaking parts of customer sites with no visible error or internal alert. Such issues often go unnoticed unless reported by an end user. * **Protect customer experience.** By separating analytics from other traffic, Coveo provides ad blockers with a clean, dedicated target. This helps ensure that search functionality and static content continue to load reliably. * **Retire outdated infrastructure.** Legacy endpoints like `cloudplatform.coveo.com` and `usageanalytics.coveo.com` are being phased out. This streamlines operations, reduces confusion, and aligns customers with current best practices. * **Enforce configuration accuracy.** Blocking misrouted calls ensures that customer implementations follow the intended architecture. This reduces the risk of future misconfigurations and improves long-term reliability. In addition, thanks to its [new organization-specific endpoints](https://docs.coveo.com/en/mcc80216/) (`.org.coveo.com`), Coveo can handle traffic to your organization in a very targeted fashion. Should an issue with your organization's traffic ever arise, Coveo will be able to handle it more efficiently. ## Do these changes impact my organization? Your organization is impacted if it does at least one of the following: * It still targets old Coveo V1 endpoints (`cloudplatform.coveo.com` and `usageanalytics.coveo.com`). You can review the endpoints in use 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)). ![Coveo Traffic panel](https://docs.coveo.com/en/assets/images/manage-an-organization/traffic-endpoint-deprecation.png) * It misuses its organization-specific endpoints in ways such as: ** Multiple organizations using the same endpoint rather than each organization using its unique endpoint. ** Making requests to a non-production organization using a production organization's endpoint, and vice versa. * It makes analytics-logging requests to search or administration endpoints, or search requests to analytics endpoints. > **Important** > > * If you're using the Coveo for Salesforce integration, see [Impacts of endpoint deprecation](https://docs.coveo.com/en/o74e0418/) for more specific information. > > * If you're using the Coveo for Sitecore integration, see [usageanalytics.coveo.com endpoint deprecation](https://docs.coveo.com/en/o6ag8284/) for more specific information. See [Detailed endpoint-related changes](https://docs.coveo.com/en/p59e8291/) for more information on the changes that will be enforced. ## Update your implementation The Coveo team has been reviewing traffic data to determine whether these changes affect your organization. If so, your Coveo representative will contact you shortly to help you update your implementation. However, since it's not possible for Coveo to review your code and rule out completely the possibility of an impact, we highly recommend that you check yourself that your Coveo implementation: * Doesn't use any of the endpoints being deprecated (`cloudplatform.coveo.com` and `usageanalytics.coveo.com`). You can review whether these endpoints receive any traffic in the [**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)) panel. * Properly uses its [organization-specific endpoints](https://docs.coveo.com/en/mcc80216/). See [Detailed endpoint-related changes](https://docs.coveo.com/en/p59e8291/) for more information on the changes that will be enforced, and make sure that your implementation doesn't violate any of them. For example, if you've built an application that makes requests to Coveo, check its code to ensure that it doesn't target any of the deprecated endpoints. If it does, you'll need to update your code to target the correct endpoint. > **Important** > > * If you're using the Coveo for Salesforce integration, see [Impacts of endpoint deprecation](https://docs.coveo.com/en/o74e0418/) for more specific information. > > * If you're using the Coveo for Sitecore integration, see [usageanalytics.coveo.com endpoint deprecation](https://docs.coveo.com/en/o6ag8284/) for more specific information. If you have any questions, contact your Coveo representative. ## Learn more * [Detailed endpoint-related changes](https://docs.coveo.com/en/p59e8291/) * [Deployment regions and strategies](https://docs.coveo.com/en/2976/) * [Organization endpoints](https://docs.coveo.com/en/mcc80216/)