Delete an export job
Deletes an export job that is completed or failed. Jobs still pending or processing cannot
be deleted or cancelled: wait for them to finish.
The job record is removed right away, so it disappears from GET /api/exports and its download
link stops working. The file itself stays on Jelliu’s storage until the cleanup sweep removes it,
at most 72 hours after it was written.
Unlike reading or downloading, deleting has no role check: any member can delete any job,
audit_log and agent_actions jobs included.
Side effects. Deletes the job record and clears the list cache. Written to the audit log as
export.delete.
Idempotency. Safe to retry. A repeated call returns 404 Export job not found.
Webhook events. Emits audit.log_recorded to webhooks subscribed to it. See Webhooks.
Access
- Required scope:
write. Any workspace role can call it. - Rate limit: General API (120–600 requests/min per workspace, by plan) plus the configuration-mutations limit — 10 requests/min per workspace, shared with other configuration changes. See Rate limits.
- Plan: Available on every plan.
Authentication
Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.
Path parameters
UUID of the export job to delete. A job of another workspace answers 404.