Endpoint deprecation and other endpoint-related changes

This is for:

System Administrator

Coveo initially went live into the cloud in 2015. Since then, technology and practices 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:

Date Enforced changes

June 3, 2025

Coveo will enforce all endpoint changes in non-production organizations and production organizations whose traffic is already 100% compliant.

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 for details.

December 1, 2025

Coveo will enforce all endpoint changes for all remaining production organizations.

The Push API endpoint, api.cloud.coveo.com/push, is not impacted by these changes.

To check whether your organization traffic is compliant with Coveo’s standards, see the Traffic (platform-ca | platform-eu | platform-au) 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.

For details on the Coveo endpoints, see Deployment regions and strategies and Organization endpoints.

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 (<orgid>.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 (platform-ca | platform-eu | platform-au).

    Coveo Traffic panel

  • 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
Important

See Detailed endpoint-related changes 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:

See Detailed endpoint-related changes 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
Important

If you have any questions, contact your Coveo representative.

Learn more