Skip to main content
The Rootprint API is the HTTP surface of your self-hosted instance: send logs and spans, query them from other tools, and automate administration. If you are setting up log collection for the first time, start with Send logs.

Base URL

All API requests go to your Rootprint instance. Replace the host below with your Rootprint host, including the port if it does not serve on the default one.

Authentication

Rootprint uses these authentication modes, depending on the endpoint. Bearer-token endpoints use the standard Authorization header.
An ingest API key writes logs to the one index it is scoped to. Spans always go to the span store; see Traces. Query API keys are read-only and read every index; see Query logs with API keys.

Common tasks

Query logs with API keys lists every endpoint that accepts a query API key. The sidebar has the full endpoint reference.

Timestamps

Request timestamps are Unix epoch seconds: startTs and endTs in query strings, and startTime/endTime in share and saved-view bodies.

Common content types

Error responses

Most app-level endpoints return JSON errors with a stable error object.
OTLP endpoints follow OTLP-style error responses instead of the app JSON error shape. Rootprint rate-limits auth and read routes; see Rate limiting. It does not rate-limit ingest endpoints, so apply a limit at your reverse proxy or load balancer if your deployment needs one.