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

# Delete OTLP destination by ID or name

`DELETE /telemetry/destinations/{id_or_name}`

## Request

- Base URL: `https://api.onkernel.com`
- URL: `https://api.onkernel.com/telemetry/destinations/{id_or_name}`
- Auth: HTTP bearer

Delete an OTLP destination. Sessions bound to it are still exporting, so the delete is refused with a 409 while any exist; either wait for those sessions to end or delete them first. It is refused the same way while a managed auth connection still selects it, because that connection re-resolves the destination on every login, and while a managed auth login using it is still in progress. Requires an organization-scoped credential or dashboard authentication; project-scoped credentials receive a 403.

## Path parameters

- `id_or_name` string, required

## Response `204`

OTLP destination deleted

## 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

## Changes

- **2026-10-16** `03b369edee49`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/kernel/apis/kernel-api/changes/telemetry/destinations/:id_or_name/delete.md)

---

[API](https://skmtc.dev/kernel/apis/kernel-api.md) - [All operations](https://skmtc.dev/kernel/apis/kernel-api/llms.txt) - [OpenAPI document](https://skmtc.dev/kernel/apis/kernel-api/revisions/0f6cf4f58fe6?raw)