OTLP ingestion
POST https://ingest.squasher.ai/v1/tracesPOST https://ingest.squasher.ai/v1/logsPOST https://ingest.squasher.ai/v1/metrics
x-squasher-key authentication header.
Successful OTLP responses confirm durable acceptance. During a telemetry-store interruption, accepted batches can enter regional recovery storage and appear after live data. Delivery is at least once, so stable OpenTelemetry event identities remain important. Retry 429 and 5xx responses with bounded exponential backoff.
Error ingestion
Required headers
x-squasher-keyContent-Type: application/jsonorapplication/x-ndjson
Accepted body shapes
Withapplication/json, send any of these shapes:
- One event object
- A top-level array of event objects
- An envelope shaped as
{ "events": [...] }
application/x-ndjson, send one event object per non-empty line. Empty, malformed, and non-object event payloads return 400 and are not forwarded.
Typical fields
messagetypestackor parsedframeslevelenvironmentreleasetags,user,request,breadcrumbs, andextra
Provider drains
POST /v1/drain/vercel/{project_id}POST /v1/drain/railway/{project_id}- Cloud provider drains documented under
/log-drains/*
AI workflow ingest
For agent sessions, model generations, and tool calls, prefer the Agent telemetry SDK. Custom senders can post Langfuse-compatible AI batches to:x-squasher-key header. See the OpenRouter direct HTTP example for a worked batch payload.