# Monitoring

Monitoring sends the organisation's own screen telemetry (OpenTelemetry metrics and events) to places it chooses, such as Datadog, New Relic, Honeycomb, Grafana Cloud, Elastic or any OTLP/HTTP endpoint. A destination holds the vendor's key, sealed: it is never shown again. A telemetry read key lets the organisation's own Prometheus, Grafana Alloy or monitoring agent pull the same metrics from `/api/v1/telemetry/metrics`. The read key starts `mtk_` and is sent as `Authorization: Bearer mtk_…`. It is not an API key: it reads this one organisation's screen telemetry and opens no other route. The answer is OpenMetrics text, at most 60 seconds old, so the route works as a scrape target for Prometheus or Alloy. Seeing and testing destinations and the presets: an editor or an owner, with Screens · Read. Changing destinations and every telemetry key route: an owner, with Settings. See [Monitoring](https://withmestra.com/docs/player/monitoring/) for the guide.

Monitoring sends the organisation's own screen telemetry (OpenTelemetry metrics and events) to places it chooses, such as Datadog, New Relic, Honeycomb, Grafana Cloud, Elastic or any OTLP/HTTP endpoint. A destination holds the vendor's key, sealed: it is never shown again. A telemetry read key lets the organisation's own Prometheus, Grafana Alloy or monitoring agent pull the same metrics from `/api/v1/telemetry/metrics`. The read key starts `mtk_` and is sent as `Authorization: Bearer mtk_…`. It is not an API key: it reads this one organisation's screen telemetry and opens no other route. The answer is OpenMetrics text, at most 60 seconds old, so the route works as a scrape target for Prometheus or Alloy. Seeing and testing destinations and the presets: an editor or an owner, with Screens · Read. Changing destinations and every telemetry key route: an owner, with Settings. See [Monitoring](https://withmestra.com/docs/player/monitoring/) for the guide.

## The Monitoring destination object

A monitoring destination: where the organisation's screen telemetry is sent. Header values are never shown.

- `id` (string (uuid), required):
- `name` (string, required):
- `preset` (string, required):  One of: `datadog`, `newrelic`, `honeycomb`, `grafanacloud`, `elastic`, `custom`.
- `endpoint` (string, required):
- `temporality` (string, required):  One of: `cumulative`, `delta`.
- `signals` (array of strings, required):
- `enabled` (boolean, required):
- `headers` (array of objects, required): The headers set, by name, with the last 4 characters of each value (empty for a short one). Never a value.
  - `name` (string, required):
  - `hint` (string, required):
- `createdAt` (string (date-time), required):
- `status` (string, required): `waiting` has not been sent to yet; `retrying` is failing and being tried again on its schedule. One of: `off`, `waiting`, `ok`, `retrying`.
- `lastOkAt` (string (date-time), required, nullable):
- `lastReason` (string, required, nullable): While retrying, a fixed code for why the last send failed (`dns`, `blocked`, `tls`, `timeout`, `connect`, `too_large`, `headers`, `status_4xx`, `status_5xx` and so on), never text from the other end.
- `lastStatus` (integer, required, nullable):
- `failingSince` (string (date-time), required, nullable):

```json
{
  "id": "string",
  "name": "string",
  "preset": "datadog",
  "endpoint": "string",
  "temporality": "cumulative",
  "signals": [
    "metrics"
  ],
  "enabled": false,
  "headers": [
    {
      "name": "string",
      "hint": "string"
    }
  ],
  "createdAt": "string",
  "status": "off",
  "lastOkAt": "string",
  "lastReason": "string",
  "lastStatus": 0,
  "failingSince": "string"
}
```

## List all monitoring presets

`GET /api/v1/telemetry/presets`

Permission: Screens · Read.

Needs an editor's or an owner's key or session (a viewer is refused). Returns the vendors a monitoring destination can be set up for (Datadog, New Relic, Honeycomb, Grafana Cloud, Elastic, or any OTLP/HTTP endpoint): each one's regions, the header its key goes in, and the metric temporality it wants, with the most destinations an organisation may have.

### Returns

The presets.

An object with:

- `presets` (array of objects, required):
  - `id` (string, required):
  - `label` (string, required):
  - `temporality` (string, required):  One of: `cumulative`, `delta`.
  - `header` (string, optional):
  - `headerHelp` (string, optional):
  - `sites` (array of objects, required):
    - `id` (string, required):
    - `label` (string, required):
    - `endpoint` (string, required):
    - `unconfirmed` (boolean, optional):
  - `endpointHelp` (string, optional):
  - `signals` (array of strings, required):
  - `eventsAvailable` (boolean, required):
- `maxDestinations` (integer, required):

### Errors

- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 409 (`api_off`): `409` with code `api_off` (“Turn on the API in Developer → API and MCP first.”): an owner hasn't turned the API on for this organisation, so no API key works yet. An owner turns it on in Settings, then API.

### Example request

```sh
curl --request GET \
  --url https://app.withmestra.com/api/v1/telemetry/presets \
  --header "Authorization: Bearer $MESTRA_TOKEN"
```

## List all monitoring destinations

`GET /api/v1/telemetry/destinations`

Permission: Screens · Read.

Needs an editor's or an owner's key or session (a viewer is refused). Returns the organisation's monitoring destinations: where its screen telemetry is sent. Each shows its status and which headers are set, with the last 4 characters of each value. A value is never shown.

### Returns

The destinations, oldest first.

An object with:

- `destinations` (array of objects, required):
  - `id` (string (uuid), required):
  - `name` (string, required):
  - `preset` (string, required):  One of: `datadog`, `newrelic`, `honeycomb`, `grafanacloud`, `elastic`, `custom`.
  - `endpoint` (string, required):
  - `temporality` (string, required):  One of: `cumulative`, `delta`.
  - `signals` (array of strings, required):
  - `enabled` (boolean, required):
  - `headers` (array of objects, required): The headers set, by name, with the last 4 characters of each value (empty for a short one). Never a value.
    - `name` (string, required):
    - `hint` (string, required):
  - `createdAt` (string (date-time), required):
  - `status` (string, required): `waiting` has not been sent to yet; `retrying` is failing and being tried again on its schedule. One of: `off`, `waiting`, `ok`, `retrying`.
  - `lastOkAt` (string (date-time), required, nullable):
  - `lastReason` (string, required, nullable): While retrying, a fixed code for why the last send failed (`dns`, `blocked`, `tls`, `timeout`, `connect`, `too_large`, `headers`, `status_4xx`, `status_5xx` and so on), never text from the other end.
  - `lastStatus` (integer, required, nullable):
  - `failingSince` (string (date-time), required, nullable):

### Errors

- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 409 (`api_off`): `409` with code `api_off` (“Turn on the API in Developer → API and MCP first.”): an owner hasn't turned the API on for this organisation, so no API key works yet. An owner turns it on in Settings, then API.
- 501 (`not_available`): `not_available`: monitoring destinations are not set up on this server.

### Example request

```sh
curl --request GET \
  --url https://app.withmestra.com/api/v1/telemetry/destinations \
  --header "Authorization: Bearer $MESTRA_TOKEN"
```

## Add a monitoring destination

`POST /api/v1/telemetry/destinations`

Permission: Settings · Write.

Needs an owner's key or session. Adds a destination that the organisation's screen telemetry (OpenTelemetry metrics and events) is sent to. The headers hold the vendor's key and are sealed: they are never returned. An organisation may have 5. Needs Mestra screens turned on.

### Parameters

- `idempotencyKey` (string, optional): Optional. Send the same value on a retry and nothing is made twice: the repeat answers 200 with the destination already made.
- `name` (string, required):
- `preset` (string, required):  One of: `datadog`, `newrelic`, `honeycomb`, `grafanacloud`, `elastic`, `custom`.
- `endpoint` (string, required): The base URL; /v1/metrics and /v1/logs are added.
- `temporality` (string, optional): The preset's when left out. One of: `cumulative`, `delta`.
- `signals` (array of strings, optional): The preset's when left out.
- `headers` (object, optional): At most 20, 8 KB in all. Sealed; never returned.

### Returns

Added.

An object with:

- `destination` (object, required): A monitoring destination: where the organisation's screen telemetry is sent. Header values are never shown.
  - `id` (string (uuid), required):
  - `name` (string, required):
  - `preset` (string, required):  One of: `datadog`, `newrelic`, `honeycomb`, `grafanacloud`, `elastic`, `custom`.
  - `endpoint` (string, required):
  - `temporality` (string, required):  One of: `cumulative`, `delta`.
  - `signals` (array of strings, required):
  - `enabled` (boolean, required):
  - `headers` (array of objects, required): The headers set, by name, with the last 4 characters of each value (empty for a short one). Never a value.
    - `name` (string, required):
    - `hint` (string, required):
  - `createdAt` (string (date-time), required):
  - `status` (string, required): `waiting` has not been sent to yet; `retrying` is failing and being tried again on its schedule. One of: `off`, `waiting`, `ok`, `retrying`.
  - `lastOkAt` (string (date-time), required, nullable):
  - `lastReason` (string, required, nullable): While retrying, a fixed code for why the last send failed (`dns`, `blocked`, `tls`, `timeout`, `connect`, `too_large`, `headers`, `status_4xx`, `status_5xx` and so on), never text from the other end.
  - `lastStatus` (integer, required, nullable):
  - `failingSince` (string (date-time), required, nullable):

### Errors

- 400 (`own_host`): A field was refused, with `field` and `code` (for example the field `endpoint` and the code `own_host`); never the value sent.
- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 409 (`not_connected`, `api_off`): `limit` (5 destinations), `not_connected` (Mestra screens are off) or `api_off`.
- 413: The body is over 16 KB.

### Example request

```sh
curl --request POST \
  --url https://app.withmestra.com/api/v1/telemetry/destinations \
  --header "Authorization: Bearer $MESTRA_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"name":"Datadog production","preset":"datadog","endpoint":"https://otlp.datadoghq.com","headers":{"dd-api-key":"<your Datadog API key>"}}'
```

## Retrieve a monitoring destination

`GET /api/v1/telemetry/destinations/{id}`

Permission: Screens · Read.

Needs an editor's or an owner's key or session (a viewer is refused). Returns one destination: its status, when it last worked, why it last failed (a fixed code) and since when it has been failing.

### Parameters

- `id` (string (uuid), required):

### Returns

The destination.

An object with:

- `destination` (object, required): A monitoring destination: where the organisation's screen telemetry is sent. Header values are never shown.
  - `id` (string (uuid), required):
  - `name` (string, required):
  - `preset` (string, required):  One of: `datadog`, `newrelic`, `honeycomb`, `grafanacloud`, `elastic`, `custom`.
  - `endpoint` (string, required):
  - `temporality` (string, required):  One of: `cumulative`, `delta`.
  - `signals` (array of strings, required):
  - `enabled` (boolean, required):
  - `headers` (array of objects, required): The headers set, by name, with the last 4 characters of each value (empty for a short one). Never a value.
    - `name` (string, required):
    - `hint` (string, required):
  - `createdAt` (string (date-time), required):
  - `status` (string, required): `waiting` has not been sent to yet; `retrying` is failing and being tried again on its schedule. One of: `off`, `waiting`, `ok`, `retrying`.
  - `lastOkAt` (string (date-time), required, nullable):
  - `lastReason` (string, required, nullable): While retrying, a fixed code for why the last send failed (`dns`, `blocked`, `tls`, `timeout`, `connect`, `too_large`, `headers`, `status_4xx`, `status_5xx` and so on), never text from the other end.
  - `lastStatus` (integer, required, nullable):
  - `failingSince` (string (date-time), required, nullable):

### Errors

- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 404 (`not_found`): `not_found`: no such destination in this organisation (another organisation's is as unknown as a missing one).
- 409 (`api_off`): `409` with code `api_off` (“Turn on the API in Developer → API and MCP first.”): an owner hasn't turned the API on for this organisation, so no API key works yet. An owner turns it on in Settings, then API.

### Example request

```sh
curl --request GET \
  --url https://app.withmestra.com/api/v1/telemetry/destinations/string \
  --header "Authorization: Bearer $MESTRA_TOKEN"
```

## Update a monitoring destination

`PATCH /api/v1/telemetry/destinations/{id}`

Permission: Settings · Write.

Needs an owner's key or session. Changes a destination's name, endpoint, signals, temporality, whether it is on, or its headers (the whole set is replaced). Moving the endpoint to another host without sending headers drops the stored key. Editing starts it afresh: its failing state is cleared.

### Parameters

- `id` (string (uuid), required):
- `name` (string, optional):
- `endpoint` (string, optional):
- `temporality` (string, optional):  One of: `cumulative`, `delta`.
- `signals` (array of strings, optional):
- `enabled` (boolean, optional):
- `headers` (object, optional):

### Returns

Changed.

An object with:

- `destination` (object, required): A monitoring destination: where the organisation's screen telemetry is sent. Header values are never shown.
  - `id` (string (uuid), required):
  - `name` (string, required):
  - `preset` (string, required):  One of: `datadog`, `newrelic`, `honeycomb`, `grafanacloud`, `elastic`, `custom`.
  - `endpoint` (string, required):
  - `temporality` (string, required):  One of: `cumulative`, `delta`.
  - `signals` (array of strings, required):
  - `enabled` (boolean, required):
  - `headers` (array of objects, required): The headers set, by name, with the last 4 characters of each value (empty for a short one). Never a value.
    - `name` (string, required):
    - `hint` (string, required):
  - `createdAt` (string (date-time), required):
  - `status` (string, required): `waiting` has not been sent to yet; `retrying` is failing and being tried again on its schedule. One of: `off`, `waiting`, `ok`, `retrying`.
  - `lastOkAt` (string (date-time), required, nullable):
  - `lastReason` (string, required, nullable): While retrying, a fixed code for why the last send failed (`dns`, `blocked`, `tls`, `timeout`, `connect`, `too_large`, `headers`, `status_4xx`, `status_5xx` and so on), never text from the other end.
  - `lastStatus` (integer, required, nullable):
  - `failingSince` (string (date-time), required, nullable):

### Errors

- 400 (`own_host`, `too_large`): Nothing to change, or a field was refused (a `field` and a code such as `own_host` or `too_large`).
- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 404 (`not_found`): `not_found`: no such destination in this organisation (another organisation's is as unknown as a missing one).
- 409 (`api_off`): `409` with code `api_off` (“Turn on the API in Developer → API and MCP first.”): an owner hasn't turned the API on for this organisation, so no API key works yet. An owner turns it on in Settings, then API.
- 413: The body is over 16 KB.

### Example request

```sh
curl --request PATCH \
  --url https://app.withmestra.com/api/v1/telemetry/destinations/string \
  --header "Authorization: Bearer $MESTRA_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"name":"Datadog (EU)","enabled":true}'
```

## Delete a monitoring destination

`DELETE /api/v1/telemetry/destinations/{id}`

Permission: Settings · Write.

Needs an owner's key or session. Deletes a destination and forgets its key and its place: nothing more is sent to it.

### Parameters

- `id` (string (uuid), required):

### Returns

Removed.

### Errors

- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 404 (`not_found`): `not_found`: no such destination in this organisation (another organisation's is as unknown as a missing one).
- 409 (`api_off`): `409` with code `api_off` (“Turn on the API in Developer → API and MCP first.”): an owner hasn't turned the API on for this organisation, so no API key works yet. An owner turns it on in Settings, then API.

### Example request

```sh
curl --request DELETE \
  --url https://app.withmestra.com/api/v1/telemetry/destinations/string \
  --header "Authorization: Bearer $MESTRA_TOKEN"
```

## Test a monitoring destination

`POST /api/v1/telemetry/destinations/{id}/test`

Permission: Screens · Read.

Needs an editor's or an owner's key or session (a viewer is refused). Sends one small test (a metric `mestra.test` of 1 and a log `Mestra test`, for the signals the destination carries) the way real telemetry is sent, and says whether it got through: `ok`, the HTTP `status` if one came back, and a fixed `reason` code when it did not. It never repeats what the other end said. One test per organisation every 10 seconds.

### Parameters

- `id` (string (uuid), required):

### Returns

The result of the test.

An object with:

- `ok` (boolean, required):
- `status` (integer, required, nullable):
- `reason` (string, required, nullable):

### Errors

- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 404 (`not_found`): `not_found`: no such destination in this organisation (another organisation's is as unknown as a missing one).
- 409 (`api_off`): `409` with code `api_off` (“Turn on the API in Developer → API and MCP first.”): an owner hasn't turned the API on for this organisation, so no API key works yet. An owner turns it on in Settings, then API.
- 429 (`too_many`): `too_many`: one test per organisation every 10 seconds; see `Retry-After`.

### Example request

```sh
curl --request POST \
  --url https://app.withmestra.com/api/v1/telemetry/destinations/string/test \
  --header "Authorization: Bearer $MESTRA_TOKEN"
```

## List all telemetry keys

`GET /api/v1/telemetry/keys`

Permission: Settings · Read.

Needs an owner's key or session, even though it only reads. Returns the organisation's telemetry read keys: the keys that read its screen telemetry from `/api/v1/telemetry/metrics`. A key is shown only when it is made; the list has each one's name, last 4 characters and last use.

### Returns

The keys, oldest first.

An object with:

- `keys` (array of objects, required):
  - `id` (string (uuid), required):
  - `name` (string, required):
  - `hint` (string, required): The last 4 characters of the key.
  - `createdAt` (string (date-time), required):
  - `lastUsedAt` (string (date-time), required, nullable):

### Errors

- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 409 (`api_off`): `409` with code `api_off` (“Turn on the API in Developer → API and MCP first.”): an owner hasn't turned the API on for this organisation, so no API key works yet. An owner turns it on in Settings, then API.
- 501 (`not_available`): `not_available`: telemetry keys are not set up on this server.

### Example request

```sh
curl --request GET \
  --url https://app.withmestra.com/api/v1/telemetry/keys \
  --header "Authorization: Bearer $MESTRA_TOKEN"
```

## Create a telemetry key

`POST /api/v1/telemetry/keys`

Permission: Settings · Write.

Needs an owner's key or session. Makes a telemetry read key (`mtk_…`). The answer is the only time the key is shown. It reads this organisation's screen telemetry and opens no other route. An organisation may have 10.

### Parameters

- `idempotencyKey` (string, optional): Optional. Send the same value on a retry and no second key is made: the repeat answers 200 with the key already made and `token` null (it was shown once).
- `name` (string, required):

### Returns

Made. `token` is shown this once.

An object with:

- `key` (object, required): A telemetry read key: the credential for `/api/v1/telemetry/metrics`. The key itself is shown once, when it is made.
  - `id` (string (uuid), required):
  - `name` (string, required):
  - `hint` (string, required): The last 4 characters of the key.
  - `createdAt` (string (date-time), required):
  - `lastUsedAt` (string (date-time), required, nullable):
- `token` (string, required, nullable): The key, `mtk_` and 43 characters. Shown once; null on a repeat of a create.

### Errors

- 400: The name was refused: the answer names the `field` and why.
- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 409 (`not_connected`, `api_off`): `limit` (10 keys), `not_connected` or `api_off`.
- 413: The body is over 16 KB.

### Example request

```sh
curl --request POST \
  --url https://app.withmestra.com/api/v1/telemetry/keys \
  --header "Authorization: Bearer $MESTRA_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"name":"Prometheus"}'
```

## Delete a telemetry key

`DELETE /api/v1/telemetry/keys/{id}`

Permission: Settings · Write.

Needs an owner's key or session. Revokes a telemetry read key: it stops working at once.

### Parameters

- `id` (string (uuid), required):

### Returns

Revoked.

### Errors

- 401 (`invalid_token`): The key is missing, unknown, revoked or expired (code `invalid_token`). Send it as `Authorization: Bearer <key>`.
- 403 (`wrong_key`): `403` for a role below the route's minimum (“Your role (\<role>) can't \<action>.”, or “Choose an organisation first.”), or, for an API key without the permission this call needs, code `wrong_key` with “This key needs the \<Area> · \<Read|Write> permission.” (for example “This key needs the Reviews · Write permission.”), or “This key can't do that.” for a call only the Mestra apps make.
- 404 (`not_found`): `not_found`: no such key in this organisation (another organisation's is as unknown as a missing one).
- 409 (`api_off`): `409` with code `api_off` (“Turn on the API in Developer → API and MCP first.”): an owner hasn't turned the API on for this organisation, so no API key works yet. An owner turns it on in Settings, then API.

### Example request

```sh
curl --request DELETE \
  --url https://app.withmestra.com/api/v1/telemetry/keys/string \
  --header "Authorization: Bearer $MESTRA_TOKEN"
```
