Archive — Ingest
POST /api/archive/documents. Puts a document into the archive. The bytes arrive
exactly one of three ways — inline base64, a staged upload reference, or a source URL the
archive fetches. Picking a file below chooses for you.
Idempotency-Key is
forwarded but not consulted. If you must not double-archive, search by
externalId first.
Without a profile version all five are required: the archive records resolved-rule evidence and permits no jurisdiction default. With a profile version, profile id and version name an exact version of your company profile and the archive resolves the rest itself — whether that version exists and is active is its decision.
uploadRef instead. That threshold is the
archive's 1 MiB inline-base64 cap, and it is unrelated to the 100 MB figure,
which decides whether a staged upload is split into parts.
Or paste base64 by hand
Leave retention empty and the resolved rule decides the floor — the normal case. If you do fill it in, the archive requires either a policy or an until-date (which must be in the future); classification and the hold flag alone are refused.