Customer Data Intake
Console-facing intake file catalog, upload, download, and schema registry endpoints.
Files
List Files
API key issued via POST /v1/{workspace_id}/api-keys. Pass the returned api_key value as a Bearer token.
500-ingested_atfalseSuccessful Response
Validation Error
Upload File
API key issued via POST /v1/{workspace_id}/api-keys. Pass the returned api_key value as a Bearer token.
^[a-z0-9][a-z0-9_-]*[a-z0-9]$Successful Response
A file in the Files list (intake-ui-mvp-design.md §5.1).
file_id — used for download.
Schema slug (UI label "Schema").
The contract version this file validated against (e.g. v1).
Null unless rejected/failed.
ISO-8601 timestamp the file was received.
The document this version belongs to (§5.9). Null for snapshot/CSV rows; set for documents — the console groups versions by it and the version chain.
The file's version number (per-document for documents, per-dataset for snapshot). Lets the UI render a document's version history.
Origin of the document this version belongs to — manual for console
uploads, google_shared_drive for the Drive connector (V269). Null for
snapshot/CSV rows.
The source's stable external id (e.g. the Google Drive file id) for the document. Lets the console show provenance and confirm a re-synced file bumped the same document. Null for manual uploads and snapshot rows.
Where the file lived within the mapped Drive folder tree (V279) — the
relative path, folder names joined by / (e.g. clinical/notes); ''
at the mapped root. Lets the console show the original folder structure. Null
for manual uploads and snapshot rows.
Validation Error
Download File
API key issued via POST /v1/{workspace_id}/api-keys. Pass the returned api_key value as a Bearer token.
Successful Response
Validation Error
No content
Schemas (Datasets)
List Schemas
API key issued via POST /v1/{workspace_id}/api-keys. Pass the returned api_key value as a Bearer token.
500nameSuccessful Response
Validation Error
Register Schema
API key issued via POST /v1/{workspace_id}/api-keys. Pass the returned api_key value as a Bearer token.
Create Schema payload (intake-ui-mvp-design.md §5.4, §5.9).
ingestion_mode is inferred from file_type (csv/xls/xlsx → snapshot;
else document) — not part of the wire contract. Snapshot datasets require
primary_key + schema; document datasets take an optional
document_processing config and ignore primary_key/schema. The backend
applies the other hidden defaults (on_schema_change=additive,
schema_version auto).
^[a-z0-9][a-z0-9_-]*[a-z0-9]$^[a-z0-9]+$Document only — the SET of accepted file types (V265, e.g.
["pdf","docx","md"]). Empty → single-type (just file_type).
file_type is included as the primary. Mixing in a tabular type
(csv/xls/xlsx) is rejected; snapshot datasets are single-type.
[]Snapshot only — the canonical PK column(s). Empty/ignored for documents.
[]Successful Response
A registered schema in the Schemas list (intake-ui-mvp-design.md §5.3).
Dataset slug (UI label "Schema").
Primary/representative file type (the first accepted type).
Document datasets: the full accepted-type set (V265). Empty for snapshot
or legacy single-type documents (the UI falls back to file_type).
[]snapshot (CSV/Excel → CDC) or document (PDF/docx → extraction).
Validation Error
External Integration Upload
API key issued via POST /v1/{workspace_id}/api-keys. Pass the returned api_key value as a Bearer token.
application/octet-streamSuccessful Response
Validation Error
Last updated
Was this helpful?

