---
title: "Delete Organization"
method: DELETE
path: "/v2/orgs/{org_id}"
tags: ["Organizations"]
---

# Delete Organization

`DELETE /v2/orgs/{org_id}`

Schedules an organization (Permit.io account) for permanent deletion.

Effective immediately, the organization disappears from `GET /v2/orgs`
(list) and direct lookups (`GET /v2/orgs/{id}`); subsequent `PATCH` and
`DELETE` calls on it return 404. To preserve recoverability during the
grace period, member grants and existing API keys are intentionally
retained — support can restore the organization until the cutoff is
reached. After the grace period the organization and all of its data
are permanently removed.

**Contract change:** This endpoint previously returned `204 No Content`
with an empty body and an immediate hard-delete. It now returns
`202 Accepted` with a JSON body describing when the permanent deletion
will occur. Existing clients that branched on `status == 204` need to be
updated.

Error responses are documented in the OpenAPI ``responses`` block above.

## Path parameters

- `org_id` string, required — Either the unique id of the organization, or the URL-friendly key of the organization (i.e: the "slug").

## Response `202`

Successful Response

- OrganizationScheduleDeleteResponse
  - `status` 'scheduled'
  - `deleted_at` string, date-time, required — Timestamp when the deletion was scheduled
  - `delete_after` string, date-time, required — Timestamp when the org will be permanently deleted

## Other responses

- `404` — Organization not found, or already scheduled for deletion.
- `409` — Concurrent deletion request detected (race between two callers).
- `422` — Validation Error

---

[API](https://skmtc.net/permit/apis/permit-io-api.md) · [All operations](https://skmtc.net/permit/apis/permit-io-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/permit/permit-io-api/versions/f3391dcb29a4/schema)