Skip to main content

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.

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.

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:
x-api-key: lqt_your_api_key_here
API keys always begin with the prefix 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.
curl -X POST https://api.lumiqtrace.com/v1/ingest \
  -H "x-api-key: lqt_your_api_key_here" \
  -H "Content-Type: application/x-ndjson" \
  --data-binary '{"event_id":"550e8400-e29b-41d4-a716-446655440000","trace_id":"trace-001","span_id":"span-001","timestamp":"2026-04-20T10:00:00.000Z","provider":"openai","model":"gpt-4o","operation":"chat","latency_ms":843,"input_tokens":512,"output_tokens":128,"cost_usd":0.0034,"status":"success","stream":false,"environment":"production","sdk_version":"1.4.2"}'

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:
Authorization: Bearer <your_session_token>
curl https://api.lumiqtrace.com/v1/events?projectId=proj_abc123 \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

Error Responses

StatusBodyMeaning
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
{
  "error": "Invalid API key"
}