API keys

API keys authenticate agents and HTTP clients. Each key belongs to a user and is bound to a namespace. Sensobit stores a hash of the key, not the plaintext.

Create a key

1. Sign in at console.sensobit.com.
2. Open API Keys.
3. Click Create New Key.
4. Set a name (prod-edge, ci-ingest) and an optional expiry in days.
5. Copy the value. It is shown once.

Plans limit how many active keys you can keep. Free workspaces start with a single key; higher plans raise the cap. See Billing.

Use a key

Send it on every ingest request:

curl -X POST https://ingest.sensobit.com/api/v1/ingest \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "X-Sensobit-Namespace: production" \
  -d '{
    "name": "demo.ping",
    "value": 1,
    "type": "gauge",
    "labels": { "host": "local" }
  }'

The Linux installer accepts the same value:

curl -fsSL https://get.sensobit.com | sudo bash -s -- --api-key YOUR_API_KEY

Query and console APIs on api.sensobit.com accept either X-API-Key or Authorization: Bearer <session-or-key>.

Rotate or revoke

1. Create a replacement key.
2. Update agents and clients.
3. Delete the old key from API Keys. Deletion is immediate.

The list view shows name, created time, last used, and expiry. It never redisplays the secret.

Safety

• Treat keys as secrets. Do not commit them to git.
• Use one key per environment or fleet so you can revoke a leaked key without stopping every host.
• Prefer short-lived keys for CI.
• File mode on /etc/sensobit/config.yaml should stay 600.