# URL Target Requirements

When creating a stream through the ThousandEyes API or UI, ensure that the Stream Endpoint URL (API) or the URL target (UI) satisfies the following conditions. Proper endpoint configuration ensures reliable data flow and integration success.

## General Requirements

* The URL must be valid and correctly formatted.
* Use HTTPS to secure the connection.
* The URL target must have a valid SSL/TLS certificate signed by a publicly trusted Certificate Authority (CA).

## Endpoint-Specific Requirements

### GRPC Targets

* GRPC endpoint URLs cannot include paths.
  * Valid example: `https://example.com`
  * Invalid example: `https://example.com/collector/v1/metrics`

### HTTP Targets

* HTTP endpoint URLs **must include the full path** to the endpoint. For example, `https://example.com/collector/v1/metrics`.

## Network Connectivity

This section applies to OpenTelemetry streaming, where ThousandEyes sends telemetry data to your collector.

### Protocol and Port

ThousandEyes uses the following for all streaming connections:

* **Protocol**: HTTPS
* **Port**: TCP 443

### Required Source IP Addresses

The URL target must be reachable from ThousandEyes at the IP addresses listed below. If the target is unreachable, the stream integration service rejects the creation request.

| **Region** | **IP Addresses**                                                                                                                                                                              |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **US1**    | `13.56.245.241`, `52.9.183.148`, `18.232.232.61`, `35.168.54.3`, `107.22.84.44`, `3.220.243.232`, `3.218.27.195`, `3.221.227.188`                                                             |
| **US2**    | `3.141.159.49`, `3.17.98.26`, `3.134.227.22`, `3.18.18.42`, `3.13.54.169`, `3.138.52.162`, `52.27.149.70`, `52.32.30.54`, `52.89.210.182`, `44.227.213.61`, `35.155.240.202`, `35.81.172.197` |
| **EU1**    | `18.157.124.37`, `3.70.3.30`, `18.158.163.183`, `35.158.19.241`, `3.127.8.252`, `46.51.169.205`, `54.75.173.76`, `54.217.22.60`, `34.243.129.225`, `54.216.15.243`, `108.128.60.238`          |

## Stream Endpoint URL in the API

In the ThousandEyes API, the URL target is referred to as the `streamEndpointUrl`. For schema definitions and more information on how to configure this parameter, see [ThousandEyes Developer Documentation: StreamEndpointUrl](https://developer.cisco.com/docs/thousandeyes/v7/streamendpointurl/).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.thousandeyes.com/product-documentation/integration-guides/opentelemetry/url-target-requirements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.