Receive Traces
OTLP/HTTP trace receiver.
Status codes are chosen around how OTel exporters behave, not around what reads nicely. An exporter retries on 5xx and on connection failure, and treats 4xx as permanent. So anything the sender could fix returns 4xx (no retry storm), and anything that is our problem must not masquerade as the sender’s fault.
Protobuf only. OTLP/JSON encodes trace and span ids as hex while protobuf’s JSON mapping expects base64, so accepting it means a bespoke conversion layer. Both LiveKit’s and Pipecat’s HTTP exporters send protobuf, so JSON buys nothing today.
Authorizations
Use Tuner API key (tr_api_...) or user session token. Find your API key in Workspace Settings > API Keys.
Response
Successful Response