Skip to main content

How tasks work

Tasks follow the same async pattern as renders:
  1. Submit a POST /v1/tasks/{type} request
  2. Receive 202 Accepted with a task_* job ID
  3. Wait for the task.completed webhook (or poll GET /v1/tasks/{id})
  4. Download the artifact via output.url or /v1/tasks/{id}/download

Task types

Common fields

All task bodies share these optional fields:

Idempotency

Task endpoints accept the same Idempotency-Key header as renders.

Endpoints