intake
Durable single-file and batch intake
Validate an immutable original and enqueue its core processing
The Idempotency-Key is scoped to the authenticated household member. Repeating the same key and semantic request returns the original documentId and taskId; reusing it for different content returns 409. By default, an already-ingested checksum returns 409 unless allowDuplicate is true. A 202 response means durable acceptance only; poll the returned taskId.
Validate two to one hundred originals as a durable intake batch
Files are processed and returned in request order. The batch envelope and item identities are durable, so repeating an identical ordered request with the same Idempotency-Key resumes or replays it. A changed filename, order, or content under that key returns 409. An intake rejection has null documentId/taskId plus a bounded error. A durable acceptance always preserves non-null documentId/taskId; while processing is active its error is null, and if processing later exhausts retries the replay preserves both IDs alongside the bounded error so clients recover the existing document rather than uploading it again.
Discover the TUS 1.0 resumable-upload capabilities
Discover the TUS 1.0 resumable-upload capabilities
Create or recover a durable resumable-upload session
Implements TUS 1.0 creation. Upload-Length is a declared original length, not a Jiandu product limit. Upload-Metadata carries base64 filename, optional conventional filetype (or Jiandu contentType), and allowDuplicate fields. Retrying an identical Idempotency-Key returns the original session Location.
Terminate one independently resumable upload
Terminate one independently resumable upload
Read transfer, finalization, and durable acceptance status
Read transfer, finalization, and durable acceptance status
Recover the authoritative durable upload offset
Recover the authoritative durable upload offset
Append one checksummed bounded transfer chunk
The per-request chunk budget bounds memory and retry cost; it is not a whole-document limit. A successful response advances Upload-Offset only after the chunk is durable.