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

# Update OTLP destination by ID or name

`PATCH /telemetry/destinations/{id_or_name}`

Update an OTLP destination. Sessions already exporting to it pick up the new values without restarting, which makes this the way to rotate credentials without interrupting export.

Names must be unique within the project. Renaming is refused with a 409 while a managed auth connection selects this destination by name, since that connection resolves the name on every login. Every other field, including `headers`, stays editable.

## Path parameters

- `id_or_name` string, required

## Request body

- OTLPDestinationUpdateRequest — Fields to update. Omitted fields are left unchanged.
  - `description` string
  - `endpoint` string — Base endpoint of the OTLP/HTTP collector, without a signal path. Same rules as on create.
  - `headers` object — Edits stored headers key by key rather than replacing the map. A string value adds or replaces that header, `null` deletes it, and any key you omit is left as it is. Names are matched case-insensitively, so `authorization` replaces a stored `Authorization` rather than adding a second entry. This is the credential rotation path; sessions already exporting pick up the new values without restarting. Names and values must be valid HTTP header tokens, and the names and values together cannot exceed 8192 bytes.
  - `name` string

## Response `200`

OTLP destination updated

- 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

- `400` — Bad Request – invalid input
- `401` — Unauthorized – missing or invalid authorization token
- `403` — Forbidden – insufficient permissions or plan
- `404` — Resource not found
- `409` — Conflict – resource already exists
- `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)