Skip to main content
DELETE
Delete Job File

Overview

Delete a single S3 object or all objects in a multi-clip delivery. The job record is retained. For a single file, the endpoint uses the current S3 configuration and the recorded s3_key; it is not a generic single-file deletion endpoint for every storage provider. Multi-clip deletion resolves and verifies the original destination before removing its objects.

Header Parameters

string
required
Your API key for authentication

Path Parameters

uuid
required
The job UUID

Response

string
Success message
string
The job ID
string
The S3 key deleted by the single-file path; absent from multi-clip responses.
integer
Number of recorded clip files deleted by the multi-clip path; absent from single-file responses.

Examples

Success Response

For a multi-clip result, a successful response is:

Error Responses

Notes

  • This requests deletion from the configured storage; provider versioning or retention policies may retain recoverable versions.
  • The job record is kept in the database for reference
  • The handler checks ownership and recorded delivery fields; it does not require the status to be Completed.
  • A single-file job without s3_key returns 400. A multi-clip job uses clip_files.
  • On Tornado-managed storage, a single-file deletion first checks that the stored object belongs to this job. It returns 409 when the object is present and cannot be proven to belong to this job, 502 when the storage check fails, 503 when storage cannot confirm ownership, and 504 on timeout. Nothing is deleted in these cases; 502, 503 and 504 can be retried.
  • A single-file deletion whose recorded storage cannot be used returns 409 and can be retried once that storage is available again.
  • On single-file success, clearing delivery metadata in Mongo is attempted; a Mongo failure is logged and does not change the 200 response.
  • Multi-clip deletion clears cached delivery data and Mongo metadata before returning 200.
For multi-clip jobs, this deletes all objects in clip_files. If the original storage credentials cannot be resolved and matched to the recorded destination, the API returns 409. An incomplete object deletion returns 502; a checkpoint or metadata failure returns 500. A partially failed deletion can be retried. The retry also succeeds when some of the original objects were already deleted by the previous attempt. Keep the same storage destination configured until the deletion finishes; changing the account, bucket or folder causes a 409.