Bulk create spans | Respan Docs

curl -X POST https://api.respan.ai/api/request-logs/bulk/ \
     -H "Authorization: Bearer <respanApiKey>" \
     -H "Content-Type: application/json" \
     -d '{
  "logs": [
    {
      "model": "gpt-4o-mini",
      "prompt_messages": [
        {
          "role": "user",
          "content": "What is 2 + 2?"
        }
      ],
      "completion_message": {
        "role": "assistant",
        "content": "4"
      },
      "metadata": {
        "source": "lambda-batch"
      }
    },
    {
      "model": "gpt-4o-mini",
      "prompt_messages": [
        {
          "role": "user",
          "content": "What is the capital of France?"
        }
      ],
      "completion_message": {
        "role": "assistant",
        "content": "Paris"
      },
      "metadata": {
        "source": "lambda-batch"
      }
    }
  ]
}'

Create up to 500 spans in one request. Each item in logs accepts the same fields as the single-span create operation. Rows are processed independently: one invalid row does not prevent the remaining rows from being accepted. A response is 201 Created whenever at least one row is accepted, including partial success; inspect error_count and errors on every response. success_count means the row passed synchronous validation and was accepted for ingestion.

For API-key authentication, this endpoint is limited to 30 requests per minute per organization, shared across all API keys in that organization. JWT requests are limited per user. At the 500-row maximum, the API-key limit allows up to approximately 15,000 accepted rows per minute. Metadata keys beginning with _ are reserved for platform use and are omitted from customer-facing span and trace responses, so they do not round-trip through read APIs.

Create up to 500 spans in one request. Each item in `logs` accepts the same fields as the [single-span create operation](/docs/apis/spans/create-span). Rows are processed independently: one invalid row does not prevent the remaining rows from being accepted. A response is `201 Created` whenever at least one row is accepted, including partial success; inspect `error_count` and `errors` on every response. `success_count` means the row passed synchronous validation and was accepted for ingestion. For API-key authentication, this endpoint is limited to 30 requests per minute per organization, shared across all API keys in that organization. JWT requests are limited per user. At the 500-row maximum, the API-key limit allows up to approximately 15,000 accepted rows per minute. Metadata keys beginning with `_` are reserved for platform use and are omitted from customer-facing span and trace responses, so they do not round-trip through read APIs.

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, provider credentials such as Perplexity, OpenAI, or Azure OpenAI go in Settings -> Providers or respan_params.credential_override in the request body, not in this authentication field.

AuthorizationBearer

Use a dashboard JWT only for dashboard-authenticated endpoints. Respan API-key endpoints use the respanApiKey auth field instead.

Request

This endpoint expects an object.

logslist of objectsRequired

Non-empty array of span payloads. Each object uses the same schema as POST /api/request-logs/.

Response

At least one row was accepted. This status is also used for partial success; inspect the response counts and indexed errors.

success_countinteger>=0

Number of items successfully processed.

error_countinteger>=0

Number of items that failed.

errorslist of objects

Item-level failures, keyed by zero-based input index.

Errors

400

Bad Request Error

401

Unauthorized Error

403

Forbidden Error

422

Unprocessable Entity Error

429

Too Many Requests Error

1	{
2	"success_count": 2,
3	"error_count": 0,
4	"errors": []
5	}