Authentication

The Datius API is authenticated with workspace API keys. Create one in the app under API Keys, give it the scopes it needs, and send it with every request.

Sending your key

Provide the key in any one of these headers:

• X-API-Key: <key>
• Authorization: Bearer <key>
• api-key: <key>, the name OpenTelemetry collectors use by convention

Scopes

A key can do only what its scopes allow:

• signals:emit: send events with the Ingestion API and the OpenTelemetry endpoints.
• signals:read: read signals, report numbers and raw events with the read API.

Give each service only what it needs: a checkout service that sends orders needs signals:emit, a nightly export job needs signals:read. Both must be workspace-scoped, and a key works only on its own workspace. Anything else is refused with 403 Forbidden.

Creating & rotating keys

Every key has an expiry between 1 and 365 days out; there's no "never expires" option. The full key is shown exactly once, when you create it. Afterwards only its prefix, name, scopes, last use and expiry are shown. To rotate a key, create a new one, move your traffic over, then revoke the old one.

The Datius web app

The web app signs you in with your Datius account and uses that session for everything you do there. Those internal endpoints aren't part of the public API and can change without notice; build on the routes in the API Reference.

Try it

The API Reference page can generate a real, short-lived test key against one of your workspaces so you can try authenticated requests directly.