Purge organization data
POST/v1/data_purges
IRREVERSIBLE: permanently deletes the chosen resources in EVERY workspace of the organization. In the dashboard the operation is confirmed with a code sent by e-mail. That is why a token that names a person (a personal or OAuth token, or a call through the MCP) gets 403: the person purges from the dashboard. Only machine tokens can purge over the API, and only when the token carries the dedicated dashboards/data_purges:write scope — granted explicitly: no other scope implies it (not write, all, dashboards/all or dashboards/admin:write); without it, 403 insufficient_scope. Their confirmation is confirm, which must repeat the organization id (from GET /organization) — a retried or mis-targeted call cannot pass by accident. Requires data.purge (organization owners only by default) and access to every workspace. Asynchronous: 202 with job_id.
Request
Responses
- 202
- 400
- 401
- 403
- 404
- 422
- 429
- 500
Purge queued; follow it on GET /data_purges/{id}.
Missing body, invalid JSON or incompatible fields.
Missing or invalid bearer token.
Token is valid but lacks permission for this operation.
Resource not found in the current organization.
confirm does not match the organization id — nothing was purged.
Rate limit exceeded.
Unexpected server error.