---
title: Remove a Telemetry Destination Workspace
url: https://platform.claude.com/docs/en/api/cli/beta/organization/telemetry_destinations/workspaces/remove
---

# Remove a Telemetry Destination Workspace

`$ ant beta:organization:telemetry-destinations:workspaces remove`

**DELETE** `/v1/organizations/telemetry_destinations/{destination_id}/workspaces/{workspace_id}`

Remove one workspace from a destination's workspace list.

Under `include` the workspace's spans stop going to the destination. Under `exclude` they start. An archived workspace can be removed too.

The API returns 404 when the workspace isn't on the list. A destination whose `workspaces.type` is `all` doesn't have a list, so the API returns 400.

See the [OpenTelemetry export guide](https://platform.claude.com/docs/en/manage-claude/opentelemetry?sdk_languages=cli#choose-workspaces-for-a-destination) to learn more about choosing the workspaces of a destination.

## Parameters

- `--destination-id: string` (path parameter)

  ID of the destination (`tdst_...`).

- `--workspace-id: string` (path parameter)

  ID of the workspace to remove (`wrkspc_...`).

- `--beta: optional array of AnthropicBeta` (header parameter)

  This endpoint is in beta: requests must send `telemetry-destinations-2026-08-11` in this header.

## Returns

- `beta_deleted_telemetry_destination_workspace: object`

  Confirmation that a workspace was removed from a destination's list.

  - `type: "telemetry_destination_workspace_deleted"`

  - `telemetry_destination_id: string`

    ID of the telemetry destination (`tdst_...`).

  - `workspace_id: string`

    ID of the workspace that was removed (`wrkspc_...`).

## Example

```bash
ant beta:organization:telemetry-destinations:workspaces remove \
  --api-key my-anthropic-api-key \
  --destination-id destination_id \
  --workspace-id workspace_id
```

### Response (200)

```json
{
  "telemetry_destination_id": "telemetry_destination_id",
  "type": "telemetry_destination_workspace_deleted",
  "workspace_id": "workspace_id"
}
```
