Delete a PDF file or an unsuccessful render

Remove a successful job's PDF from storage, or remove a failed or cancelled job from history. The job stays readable by ID, and billing, abuse limits, and idempotency keys stay unchanged. The file is removed before its database marker; a file-removal failure returns 500 and leaves the record live for a safe retry. Repeated requests are safe. At or after the file's retention end, the removal reason remains expired.

delete/v1/pdf/{id}

Request

  • Base URL: https://thirds.ai
  • URL: https://thirds.ai/v1/pdf/{id}
  • Auth: HTTP bearer

Path parameters

idstring required

The job's public identifier, such as "pdf_1f8b3c7d5e2a49061f8b3c7d5e2a4906".

Response

The job's current status after file or history removal.

referencestring

Your reference, preserved in the job, history, and webhook. Omitted when not supplied.

idstring required

The job's public identifier: "pdf_" followed by 32 lowercase hexadecimal characters.

status'queued' | 'running' | 'succeeded' | 'failed' | 'cancelled' required
created_atstring date-time required
finished_atstring date-time nullable required
credit'reserved' | 'settled' | 'released' | 'free' | 'none' required

What happened to the credit this job holds: "reserved" while it is queued or running, "settled" once it succeeded, "released" once it failed or was cancelled, "free" when it is the account's free first file and costs no credit, and "none" when the job was never billed.

Changes

No recorded changes to this operation across all 1 revision of this API.