---
search:
  tags:
    - Ingest keys
    - POST
seo:
  description: >-
    Create a fixed key for a long-running service. Send it as Authorization:
    Bearer… Reference for the POST /v1/ingest-keys endpoint in the sigiro API
    Reference.
sidebar:
  label: Create an ingest key
  badge: POST
title: Create an ingest key
type: openapi-operation
---
Create a fixed key for a long-running service. Send it as `Authorization: Bearer <key>` (for example `OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <key>"`). It sends telemetry to this workspace and cannot read anything. The response is the only time the key is shown: only its hash is stored.

`POST /v1/ingest-keys`

**Request body** (`application/json`, required)

- `name` (string | null) — A label to tell keys apart, such as the service that uses it. 1 to 64 characters; defaults to "ingest key".

Request body example:

```json
{
  "name": "string"
}
```

**Responses**

- `201` — The new key, shown once
- `400` — Invalid name, or the workspace already has 50 active keys
- `401` — Missing or invalid bearer token
- `403` — Not a user's own OAuth access token

Response example, 201:

```json
{
  "created_at": "string",
  "created_by": "string",
  "id": "string",
  "last_used_at": "string",
  "name": "string",
  "revoked_at": "string",
  "key": "string"
}
```