Stream logs

Send a batch

POST /v1/ingest/sources/{source_key}/logs accepts a batch of records and returns 202 Accepted. The records are queued and become searchable once indexed.

Authenticate with the source’s ingest token as a bearer credential — the token already names the source and tenant, so no X-Splendor-Tenant-Id header is needed. Send the batch as a top-level JSON array (Content-Type: application/json), or as newline-delimited JSON, one object per line (Content-Type: application/x-ndjson). Gzip is allowed.

curl https://api.withsplendor.com/v1/ingest/sources/app-logs/logs \
  -H "Authorization: Bearer $SPLENDOR_INGEST_TOKEN" \
  -H "Content-Type: application/json" \
  -d '[
    {"level": "error", "message": "connection timeout after 30s", "service": "checkout"},
    {"level": "info", "message": "request completed", "service": "checkout"}
  ]'

client.post(
    "/v1/ingest/sources/app-logs/logs",
    headers={"Authorization": f"Bearer {ingest_token}", "Content-Type": "application/json"},
    json=[
        {"level": "error", "message": "connection timeout after 30s", "service": "checkout"},
        {"level": "info", "message": "request completed", "service": "checkout"},
    ],
)

The response includes how many records were received and a fragment_id for the batch.

A 202 means the batch was accepted, not that it is searchable yet. Track progress with ingest runs or dataset readiness.

Get started

Core concepts

Guides

Build a platform

Roles, permissions & plans

Platform reference

Prerequisites

Send a batch

Ingest a dataset

Run a search

​Prerequisites

​Send a batch

​Related

Ingest a dataset

Run a search

Prerequisites

Send a batch

Related