API reference

Traces (OTLP)

Endpoint POST /v1/traces

OpenTelemetry SDKs and Collectors export spans here. Sentry SDKs send transactions through the envelope endpoint instead and end up in the same table.

1Request

X-Blipit-Key or Authorization: Bearer, public or secret. OTLP/HTTP JSON body up to 4 MB, gzip, deflate or brotli accepted, at most 1,000 spans per request. service.name from the resource names the service; server and consumer spans and roots become transactions. Descriptions are cut at 1,000 characters (db statements 2,000); 32 tags of 256 characters each are kept.

ini

OTEL_EXPORTER_OTLP_ENDPOINT=https://in.blipit.io
OTEL_EXPORTER_OTLP_PROTOCOL=http/json
OTEL_EXPORTER_OTLP_HEADERS=x-blipit-key=<public key>
OTEL_SERVICE_NAME=shop-api

2Responses

200 {accepted: true, spans: n}. 202 {accepted: false, reason: 'monthly span allowance used up'}. 400 unreadable JSON. 413 more than 1,000 spans. 415 protobuf content type. 401 unknown key.

Good to know

Spans per month: Free 1M, Solo 5M, Team 20M, Scale 100M; kept 7 days on Free and Solo, 30 on Team and Scale.
gRPC and protobuf are not read; keep the protocol on http/json.

Stuck? Email support@blipit.io. Keys and the exact DSN for each project are under API keys in app.blipit.io.