---
title: "Delete Job"
method: DELETE
path: "/jobs/{job_id}"
tags: ["Jobs"]
---

# Delete Job

`DELETE /jobs/{job_id}`

## Request

- Base URL: `https://api.hedra.com/v3`
- URL: `https://api.hedra.com/v3/jobs/{job_id}`
- Auth: one of:
  - API key in header `Authorization`
  - HTTP bearer

Delete a finished job's outputs, prompt and logs.

Afterwards `GET /v3/jobs/{job_id}` reports each output `EXPIRED`, with no
prompt and no logs, and `GET /v3/jobs` still lists the job with its model,
status, timestamps and cost. Another job whose output this job read by
`asset_id` is unchanged. Deleting a job again returns 204.

Returns 409 `ALREADY_IN_PROGRESS` while the job, or another job that names
this job's output by `asset_id`, is `IN_QUEUE` or `IN_PROGRESS`; 400
`INVALID_ARGUMENT` for a voice clone job; and 503 `UNAVAILABLE` when Hedra
could not finish deleting the job. Retry the request to finish it.

## Path parameters

- `job_id` string, required: The job's id (`job_<uuid>`).

## Response `204`

Successful Response

## Other responses

- `400`: Invalid or failed-validation request.
- `401`: Authentication failed: missing, malformed, or invalid credentials.
- `403`: Insufficient scope or plan.
- `404`: Resource not found.
- `409`: The job, or another job that names its output by `asset_id`, is `IN_QUEUE` or `IN_PROGRESS`. Retry once it has finished.
- `429`: Rate limit exceeded.
- `500`: Internal error.
- `503`: Hedra could not finish deleting this job. Retry the request.

## Changes

- **2026-10-16** `06692d16e78a`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/hedra-labs/apis/hedra-api/changes/jobs/:job_id/delete.md)

---

[API](https://skmtc.dev/hedra-labs/apis/hedra-api.md) - [All operations](https://skmtc.dev/hedra-labs/apis/hedra-api/llms.txt) - [OpenAPI document](https://skmtc.dev/hedra-labs/apis/hedra-api/revisions/6ef35a11cefe?raw)