Ingestion API
Logs are ingested into LogClaw exclusively via OTLP (OpenTelemetry Protocol). The OTel Collector accepts both gRPC and HTTP transports.Send Logs (HTTP/JSON)
string
default:"POST"
HTTP method
POST https://otel.logclaw.ai/v1/logs
Via Dashboard proxy (self-hosted): POST /api/otel/v1/logs
Direct (self-hosted): POST http://logclaw-otel-collector:4318/v1/logs
Authentication
LogClaw Cloud requires an API key via the
x-logclaw-api-key header. Get your key from console.logclaw.ai under Settings → API Keys. See API Keys for details.Self-hosted deployments do not require authentication — access is controlled at the Kubernetes NetworkPolicy level.Request Headers
Request Body
Response
200 OKpartialSuccess object means all records were accepted.
OTLP Field Reference
Attribute Value Types
OTLP attributes support multiple value types:Send Logs (gRPC)
LogClaw Cloud (managed):grpc://otel.logclaw.ai:443
Direct (self-hosted): grpc://logclaw-otel-collector:4317
Use the OTLP gRPC exporter from any OpenTelemetry SDK. This is the recommended transport for production workloads — binary Protobuf is more compact and efficient than JSON.
LogClaw Cloud gRPC uses TLS on port 443. Set your SDK’s
insecure option to false (the default). Authentication via x-logclaw-api-key header is required — the same as HTTP.