Skip to main content
Splendor is a search and retrieval API for your operational data. You ingest datasets — logs, documents, and structured records — and query them through one consistent interface that spans full-text, SQL, and semantic (vector) search. Every record carries provenance back to its source, and every dataset is isolated to your tenant. The API is organized around a few ideas that recur everywhere:
  • Datasets hold your ingested records and expose a schema you can query.
  • Search runs over one or more datasets in text, sql, or semantic mode and returns a single shared envelope.
  • Handles — a search_id, view_id, or cursor — let you page, export, and re-run a query without copying results around.
  • Provenance ties each result back to the exact source object and line it came from.

​
Start here

Quickstart

Run your first search in a few minutes with curl, Python, or TypeScript.

Authentication

Authenticate with a bearer token and select your tenant.

Core concepts

Understand datasets, the search model, handles, views, and provenance.

API reference

Browse every endpoint with request and response schemas.

​
How a request is shaped

Every authenticated request carries two things: a bearer token that identifies you, and a tenant header that selects which workspace you are acting in. 
curl https://api.withsplendor.com/v1/datasets \
  -H "Authorization: Bearer $SPLENDOR_TOKEN" \
  -H "X-Splendor-Tenant-Id: $SPLENDOR_TENANT_ID"
From there, the same envelope and the same handles apply whether you are running a keyword search, a SQL projection, or a semantic lookup. The next pages walk through each piece.