/
v1 · stable
Reference

API keys & scopes

Keys are how everything authenticates to Inkvo — collectors, CI, and read clients. Scopes keep each one to exactly what it needs.

Scopes

ScopeGrantsTypical holder
ingest:*Write traces, metrics, logs, deploysOTel collector
deploys:writeSend deploy markers onlyCI pipeline
read:incidentsRead incidents & narrativesBI / dashboards
admin:*Full workspace controlHumans, sparingly

Rotation

Keys are shown exactly once at creation. Rotate by creating a new key, deploying it, then revoking the old one — both work during the overlap so there's no ingest gap. Every create and revoke lands in the audit log.

One key per environment per purpose
Don't share a key across prod and staging. Scoping by environment is what makes the audit trail and blast-radius math trustworthy.