Detailed endpoint-related changes

This is for:

System Administrator

As explained in Endpoint deprecation and other endpoint-related changes, Coveo is making changes to its endpoints and the requests they accept. This page details the changes that Coveo will enforce in 2025.

Make sure that your organization is compliant with these changes before the enforcement date. Otherwise, your search and analytics traffic will be blocked, which will impact your search experience and analytics data.

Change 1: Block analytics-logging requests made towards search and administration endpoints

Coveo will block analytics-logging requests made towards search (search.cloud.coveo.com/*) and administration (platform.cloud.coveo.com/*) endpoints (and their regional variants).

The following requests will be blocked:

  • /rest/v15/analytics/**

  • /rest/v14/analytics/**

  • /rest/ua/v?*/analytics/

  • /rest/organizations/{organizationId}/events/**

Analytic data logged by these requests will be lost. Other requests made to the search and administration endpoints will not be blocked.

This change will be enforced in two phases:

  1. On June 3, 2025 for all non-production organizations, as well as for production organizations whose traffic is already 100% compliant.

  2. October 1, 2025 for all remaining production organizations.

Change 2: Deprecate the Coveo V1 endpoints

Coveo will deprecate the Coveo V1 platform endpoint (cloudplatform.coveo.com) and the Coveo V1 usage analytics endpoint (usageanalytics.coveo.com). Requests made to these endpoints will be blocked.

This change will be enforced in two phases:

  1. On June 3, 2025 for all non-production organizations, as well as for production organizations whose traffic is already 100% compliant.

  2. December 1, 2025 for all remaining production organizations.

Change 3: Block non-analytics requests made to the analytics endpoints

Coveo will block all non-analytics requests made to the analytics endpoint analytics.coveo.com/*.

All requests will be blocked, except for the following:

  • /rest/v15/analytics/**

  • /rest/v14/analytics/**

  • /rest/ua/v?*/analytics/

  • /rest/organizations/{organizationId}/events/**

This change will be enforced in two phases:

  1. On June 3, 2025 for all non-production organizations, as well as for production organizations whose traffic is already 100% compliant.

  2. December 1, 2025 for all remaining production organizations.

Change 4: Block requests to wrong organization-specific endpoints

Coveo will block requests made to an organization-specific endpoint that target a different organization.

For example, a query targeting organization /rest/organizations/myproductionorg sent to mysandboxorg.org.coveo.com will be blocked because it’s incoherent, while the same query via myproductionorg.org.coveo.com will be allowed.

This change will be enforced in two phases:

  1. On June 3, 2025 for all non-production organizations, as well as for production organizations whose traffic is already 100% compliant.

  2. December 1, 2025 for all remaining production organizations.