Ingest spans from traces (v1 legacy)

Legacy trace-ingest endpoint. Accepts spans either as a raw JSON array or as an object with a data field containing the span array. Each span uses the same fields as Create a span, plus trace_unique_id, span_unique_id, and optional span_parent_id to build the trace tree. For new integrations, prefer Create a trace (OTLP).

Legacy trace-ingest endpoint. Accepts spans either as a raw JSON array or as an object with a `data` field containing the span array. Each span uses the same fields as [Create a span](/docs/apis/spans/api-request-logs), plus `trace_unique_id`, `span_unique_id`, and optional `span_parent_id` to build the trace tree. For new integrations, prefer [Create a trace (OTLP)](/docs/apis/traces/create-trace).

Authentication

AuthorizationBearer

Use your Respan API key for Respan API authentication. Enter only the Respan API key value; clients send Authorization: Bearer <RESPAN_API_KEY>. For /api/responses, OpenAI or Azure OpenAI provider credentials go in Settings -> Providers or the request body credential_override field, not in this auth field.

Request

This endpoint expects a list of objects or an object.

list of objectsRequired

Array of span objects to ingest as traces.

objectRequired

Wrapper object accepted by the legacy integration endpoint.

Response

Trace spans processed successfully

messagestring

Human-readable ingest summary.

Errors

400

Bad Request Error

401

Unauthorized Error

500

Internal Server Error

$	curl -X POST https://api.respan.ai/api/v1/traces/ingest \
>	-H "Authorization: Bearer <respanApiKey>" \
>	-H "Content-Type: application/json" \
>	-d '[
>	{
>	"trace_unique_id": "trace_abc123",
>	"span_unique_id": "span_001"
>	}
>	]'