Delete a document

Moves a document to the trash, which is reversible. There is no permanent delete: retrying a failed batch cannot destroy anything.

DELETE /v1/documents/:id

Permission

The key must be granted docs.documents.write

A key without it gets 403 insufficient_scope, with the missing permission named in details.

Moves it to the trash, which is reversible with the restore endpoint. A permanent delete is not exposed at all, so an integration retrying a failed batch cannot destroy a customer's work.

Path parameters

Field	Type	Description
`id` required	string	The document to trash.

Request

curl https://api.veruapis.com/v1/documents/:id \
  -X DELETE \
  -H "Authorization: Bearer vak_live_..." \
  -H "Idempotency-Key: $(uuidgen)"

Idempotency-Key is required on every write. Retrying with the same key returns the original response rather than repeating the operation, so a timeout is something you retry rather than something you investigate.

Response

Answers 204.

{
  "data": 204 No Content,
  "meta": { "request_id": "req_01j8z9...", "timestamp": "2026-09-02T10:00:00Z" }
}

Worth knowing

Trash, not destruction, and reversible with restore. There is no permanent delete on this API at all.

Errors

Every failure uses the same shape, with a stable string code you can branch on. See the error reference.

DELETE `/v1/documents/:id`

Your API key Used once, never stored.

id

Delete a document

Permission

Path parameters

Request

Response

Related