Schedule a Mist for destruction (15-day grace)
Schedules the Mist for deletion 15 days out. The state changes to
pending_destroy and scheduled_destroy_at is set. The app’s
repository, database, and deployment stay intact throughout the
grace period, so an accidental delete can be undone without data
loss with POST /api/v202604/mists/{mist_id}/restore.
While the Mist is pending_destroy, you can still read and
restore it, but its env var, domain, deployment, and log
endpoints return 409. When the grace period ends, the
app’s resources are permanently torn down.
Returns 409 if the Mist is already pending_destroy.
Requires a company admin token with the mist.destroy permission.
Authorizations
Bearer token authentication. Accepts company admin tokens with
the matching mist.* permission:
mist.viewto list and show Mistsmist.createto create and rename Mistsmist.destroyto delete and restore Mistsmist.codefor deployments and logsmist.env_varsto read and manage environment variables Droplet installation tokens are refused.
Path Parameters
UUID of the company-owned Mist app.
Response
Scheduled for destruction. The response carries the mist
with state: "pending_destroy" and a non-null
scheduled_destroy_at.
One Mist hosting — the deployed extension with its repo, database, and Vercel project.