Temlavo

API reference

Delete document

Delete a document to end API access and clear its stored results and document fields. Storage deletion is attempted immediately and retried if needed. Separate account and financial records follow their own retention rules, as described below.

On this page

DELETE/v1/documents/{document_id}

Path parameters

document_idstringrequired

The doc_… identifier of an account-owned document.

Responses

  • 204 - deleted from the API. Stored results and document fields are cleared; physical storage cleanup may still be pending.
  • 404 - unknown document. An authoritative 404 is never reinterpreted as success; after an ambiguous transport failure, one bounded retry of the exact same DELETE is allowed.
  • 429 - throttled; treat Retry-After as a minimum delay.

Deletion semantics

DELETE is idempotent for an account-owned live resource or a retained tombstone within the retention window. Deletion serializes on the document row: if deletion wins before processing completes, the document is never resurrected or billed, and provider cancellation is best-effort.

Deleting one document never affects other documents in the same accounting_entity_id namespace.

The account's separate discovery index retains raw accounting-entity IDs and first/last-seen timestamps for the active account lifetime. Document deletion does not close the account or remove that index, required financial/security records, Vercel platform logs, or copies in your own systems. See the Privacy Notice's retention and account-closure details.

What deletion removes, and what retention keeps