Skip to main content

Prompt Hub API

Vault API

Rule Engine API

Manage Models API

​
Product surfaces

In addition to the SDK-facing endpoints above, the OpenLIT client ships an interactive OpenAPI reference at Settings → OpenAPI Spec (/openapi-spec). That catalog also covers:
  • AI Analysis — GET/POST /api/chat/improvement/{spanId} for saved runs and streaming reviews of traces/spans
  • Ask Otter — /api/chat/* for config, conversations, streaming messages, SQL execute, widgets, and usage
  • Telemetry — logs, metrics, traces, exceptions, and span hierarchy APIs
See AI Analysis and Chat with Otter for product docs.

​
Request context headers

OpenLIT scopes data by Organisation → Project → Environment. Signal routing (latest) picks the connector for each signal from the active project + environment.

​
Non-SDK APIs (telemetry, Ask Otter, AI Analysis, …)

Use signal routing headers only. Do not send x-openlit-database-config-id. The API key still binds a vault/credential database config (middleware injects x-database-config-id).

​
SDK-facing APIs (Prompt Hub, Vault, Rule Engine)

Prefer signal routing (project + environment) to resolve the intelligence ClickHouse that stores prompts, secrets, and rules. Existing SDKs that only send Authorization: Bearer … keep working via the API key’s bound database config. Those endpoints also accept an explicit x-openlit-database-config-id when it belongs to the same project as the key.

​
Authentication

All documented endpoints require an Authorization header:
Manage Models UI pages also accept a signed-in OpenLIT session in the browser. The public pricing export requires no auth.