Get started

Authentication

Every request authenticates with an API key passed as a bearer token. Keys map to a tenant, and every resource is scoped to that tenant.

API keys#

Pass your key as a bearer token in the Authorization header on every request. Keys are stored only as a one-way hash, never in plaintext, so copy yours when it is provisioned. A key can be revoked instantly; a revoked key is rejected on its next use.

bash

curl https://api.lirovo.ai/v1/schemas \
  -H "Authorization: Bearer $LIROVO_API_KEY"

Getting a key

API keys are provisioned through onboarding today (operator-provisioned). See API reference: authentication for the API-level details.

Tenancy and isolation#

Lirovo is multi-tenant from day one. Every schema, job, result, artifact, and destination is scoped to the tenant that owns the key, with no cross-tenant reads. If the tenant behind a key is suspended or deleted, the request is rejected on every call, regardless of the key's own status.

Request tracing#

Every response returns an x-lirovo-request-id header. Paste that value when contacting support so the exact request can be traced, whether it succeeded or failed.