Cancel or delete a task

DELETE /v1/contents/generations/tasks/{id} is the native Seedance cancel/delete verb. What it does depends on the task’s current state — Aurous mirrors the provider’s state machine.

Scope: write
Auth: X-Api-Key: al_live_… or Authorization: Bearer al_live_…

cURL

curl -X DELETE https://api.aurous-labs.com/v1/contents/generations/tasks/vid_01J9Z3K7Q0XY2ABCDEFGHJKMNP \
  -H "X-Api-Key: al_live_…"
# → HTTP 200  {}

A successful cancel or delete returns HTTP 200 with an empty object {}.

State machine

Task state	What `DELETE` does	Response
Queued (not yet running)	Cancels the task and releases the credit hold in full — you are charged 0. A `video.cancelled` webhook fires.	`{}` (200)
Running	Cannot be cancelled. The provider refuses; Aurous forwards its refusal (status + body) verbatim.	provider-shaped error
Terminal (`succeeded` / `failed` / `expired`)	Hides the record from retrieve and list. Money and audit rows are never hard-deleted.	`{}` (200)
Already cancelled	Refused (provider parity) — a cancelled task cannot be cancelled again.	provider-shaped error

Cancelling while queued is your lever to free pinned credits. A task’s hold can pin credits until it runs (or until execution_expires_after). If you no longer need a queued task, delete it — the hold releases immediately and the charge is 0. Once the task is running it can no longer be cancelled, and it will settle normally on success.

Errors

Code	HTTP	When
`resource_not_found`	404	Unknown id, another team’s task, or an already-hidden task. Indistinguishable by design.
`insufficient_scope`	403	The API key lacks the `write` scope.

A refusal on a running or already-cancelled task is returned in the provider’s own error shape, not remapped — that is the raw contract. See Errors for the envelope and support workflow.

Get started

Guides

Concepts

API Reference

Resources

Cancel or delete a task

State machine

Errors

​State machine

​Errors

State machine

Errors