TamaDB API Catalogue

Complete REST API reference for TamaDB Increment 1 — all ~46 endpoints grouped by domain.

Endpoints by Category

• Schemas (6 endpoints)
• Document_Types (5 endpoints)
• Channels (9 endpoints)
• Ingestion (2 endpoints)
• Documents (6 endpoints)
• Subscriptions (4 endpoints)
• Quarantine (2 endpoints)
• Configuration (15 endpoints)
• Health & Admin (2 endpoints)

Conventions

• All endpoints return JSON. Request bodies (where applicable) must be Content-Type: application/json.
• Path parameters are shown as {paramName}.
• The health endpoint is the only one not under the /api/v1 prefix.
• Composed D-Ids (multi-field identity) use : as delimiter in URLs.
• TamaDB uses upsert semantics — there is no separate create vs update for documents.

Error Response Shape

All error responses follow a consistent structure:

{
  "code": "ERROR_CODE",
  "message": "Human-readable description",
  "quarantineRef": "qr-xxx-nnnn"  // only if quarantined
}

Common Error Codes

Code	HTTP	Meaning
PARSE_ERROR	400	Payload is not valid JSON
SCHEMA_VALIDATION_FAILED	422	Document doesn't match schema
DOCUMENT_TYPE_NOT_FOUND	404	No such Document_Type registered
CHANNEL_NOT_FOUND	404	Channel doesn't exist
CHANNEL_INACTIVE	403	Channel suspended by operator
CHANNEL_BLOCKED	403	Channel blocked due to schema conflict
VERSION_CONFLICT	409	Optimistic concurrency mismatch
ENRICHMENT_CONFLICT	409	Payload conflicts with enrichment bindings
DOCUMENT_NOT_FOUND	404	Document doesn't exist or is soft-deleted

Document version: 1.0 — August 2026. Corresponds to: TamaDB Increment 1