---
title: "Get OTLP destination by ID or name"
method: GET
path: "/telemetry/destinations/{id_or_name}"
tags: ["Browser Telemetry"]
---

# Get OTLP destination by ID or name

`GET /telemetry/destinations/{id_or_name}`

Retrieve a single OTLP destination in the resolved project by its ID or name.

## Path parameters

- `id_or_name` string, required

## Response `200`

OTLP destination details

- OTLPDestination — An OTLP endpoint to export browser session telemetry to. Reference one from `telemetry.export.otlp.destination` when creating a browser to export that session's captured telemetry to it.
  - `created_at` string, date-time, required
  - `description` string
  - `endpoint` string, required — OTLP/HTTP endpoint telemetry is sent to.
  - `headers` object, required — Headers sent with each export request. Names are returned in canonical form (`Authorization`, not `authorization`). Values are returned redacted as empty strings, so the keys are visible but the credentials are not.
  - `id` string, required
  - `name` string, required — Unique within the project. Usable in place of the ID when selecting a destination, so it cannot be shaped like an ID.
  - `updated_at` string, date-time, required

## Other responses

- `401` — Unauthorized – missing or invalid authorization token
- `403` — Forbidden – insufficient permissions or plan
- `404` — Resource not found
- `500` — Internal Server Error

---

[API](https://skmtc.net/onkernel/apis/kernel-api.md) · [All operations](https://skmtc.net/onkernel/apis/kernel-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/onkernel/kernel-api/revisions/858365328f92/schema)