LumiqTrace uses two authentication methods depending on the type of request you are making. SDK ingest requests use an API key passed as a request header, while dashboard data, metrics, and AI endpoints use a session-based Bearer token. Both methods require you to include credentials on every request — the API does not use cookies for machine-to-machine calls.Documentation Index
Fetch the complete documentation index at: https://docs.lumiqtrace.com/llms.txt
Use this file to discover all available pages before exploring further.
API Key Authentication
Use your project API key to authenticate calls to the ingest endpoint (POST /v1/ingest). API keys are project-scoped, meaning each key can only write events to the project it belongs to.
Pass the key in the x-api-key header:
lqt_. You can create and revoke keys from Settings → API Keys in the LumiqTrace dashboard.
Keep your API key secret. If a key is compromised, revoke it immediately from the dashboard and generate a new one. Your existing data is not affected.
Bearer Token Authentication
Use a Bearer token to authenticate calls to data, metrics, and AI endpoints. You obtain a token by signing in to the LumiqTrace dashboard or via the/v1/auth/login endpoint.
Pass the token in the Authorization header:
Error Responses
| Status | Body | Meaning |
|---|---|---|
401 | { "error": "Invalid API key" } | The x-api-key header is missing or the key does not exist. |
401 | { "error": "Not authenticated" } | The Authorization header is missing or the Bearer token is expired. |
403 | { "error": "Not a member of this organization" } | Your credentials are valid but you do not have access to the requested organization or project. |
Example 401 response