---
title: Validate routes
slug: '2535'
canonical_url: https://docs.coveo.com/en/2535/
collection: coveo-for-sitecore-v5
source_format: adoc
---
# Validate routes
> **Important**
>
> Coveo will deprecate v1 endpoints on June 3, 2025.
> Visit [usageanalytics.coveo.com endpoint deprecation](https://docs.coveo.com/en/o6ag8284/) to determine if this change affects you and, if necessary, learn how to update your Coveo for Sitecore configuration.

This article is intended for developers and administrators who need an in-depth view of the interactions occurring between the Coveo for Sitecore package services and the [Coveo Platform](https://docs.coveo.com/en/186/).
You can use the following information to add the necessary URLs to your firewall exceptions.

## Topology of services and components


[.version.c4sc.c4sc-new.5-0-858-1.December-11&-2020]
[Coveo for Sitecore 5.0.858.1](https://docs.coveo.com/en/3408#release-notes)


New Coveo for Sitecore activations use [organization endpoints](https://docs.coveo.com/en/mcc80216/) which automatically route requests to the region-specific endpoints.

> **Note**
>
> For instructions on enabling organization endpoints in Coveo for Sitecore, see [Migrate to organization endpoints](https://docs.coveo.com/en/o1ud0002/).

The following diagram illustrates the topology of services and components involved with Coveo for Sitecore.

![Topology of services | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/topology-of-services.png)

* Pushing Sitecore documents to a Coveo index is a two-step process comprising a call to the Amazon AWS endpoint and another to the Coveo Push API endpoint (see [Manage batches of items in a Push source](https://docs.coveo.com/en/90/)).

See [IP Addresses to Allowlist](https://docs.coveo.com/en/1831/) for a complete list of IP addresses Coveo uses for its inbound and outbound communications.

## Endpoints your Sitecore instance uses


[.version.c4sc.c4sc-new.5-0-858-1.December-11&-2020]
[Coveo for Sitecore 5.0.858.1](https://docs.coveo.com/en/3408#release-notes)


The **Coveo Organization** section of the **Command Center** now contains a **Coveo Platform Endpoints** subsection which lists the specific endpoints your Sitecore instance is using, combined with a **Copy to clipboard** functionality.

![Platform Endpoints in Command Center | Coveo](https://docs.coveo.com/en/assets/images/c4sc-v5/organization-endpoints.png)

## Validating routes #1-6 (from Sitecore to Coveo)

Coveo for Sitecore uses routes 1 to 6 for the following purposes:

[%header,cols="1,5"]
|===
|Route
|Purpose

|Route 1
|The [Push API endpoint](https://platform.cloud.coveo.com/docs?urls.primaryName=PushAPI) is used to push documents and permissions to Coveo when indexing Sitecore content.

|Route 2
|The platform endpoint is used as a fallback to perform administrative API calls, manage [Coveo Platform](https://docs.coveo.com/en/186/) resources (for example, creating sources and fields), and to perform search queries.

|Route 3
|The [admin organization endpoint](https://docs.coveo.com/en/mcc80216#admin-endpoint) is used to perform administrative API calls.

|Route 4
|The [search organization endpoint](https://docs.coveo.com/en/mcc80216#search-endpoint) is used to query Coveo for Sitecore indexes.

|Route 5
|The [analytics organization endpoint](https://docs.coveo.com/en/mcc80216#analytics-endpoint) is used to send Coveo for Sitecore activity data to Coveo.

|Route 6
|The [Amazon AWS endpoint](https://docs.coveo.com/en/43/) is used to push documents and permissions to Coveo using a Push API file container.
|===

To validate the routes

. On the Sitecore server, open a web browser and access each of the specific [endpoints your Sitecore instance uses](#endpoints-your-sitecore-instance-uses).

. You should be able to reach each URL.

## Validating route #7 (from Sitecore to Sitecore through the load balancer)

This route is used by the [`FetchPageContentProcessor`](https://docs.coveo.com/en/2326/) and [`HtmlContentInBodyWithRequestsProcessor`](https://docs.coveo.com/en/2327/) processors to retrieve the page content.

To validate the route

> **Important**
>
> If Sitecore is secure, the protocol is HTTPS and the port is 443.

. On the Sitecore server, open a web browser and access `\http://<LOAD_BALANCER_HOSTNAME>/coveo/rest`.

. You should get an output similar to this:

![Screenshot of the Coveo slash Rest page in the browser which shows the default unfiltered search query results JSON](https://docs.coveo.com/en/assets/images/c4sc-v5/37099717.png)