# Delete a permission group

```http
DELETE https://secure.yoprint.com/v1/api/store/{team_slug}/setting/group/{hash_id}
```

- API version: v1
- Operation ID: `v1_public_group_destroy`
- Section: Team settings › [Permission groups](https://developer.yoprint.com/reference/permission-groups.md)
- Web page: https://developer.yoprint.com/reference/permission-groups/v1-group-destroy/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Deletes a permission group for good. A group that still has members cannot be deleted; move them to another group first.

## Permission

Needs the Manage Settings permission. The team's plan must include advanced permission management.

## Business rules

- The group must have no members.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `hash_id` (string, required): The permission group's `id`: a hash id from an earlier answer. Only hash ids work here; anything else answers 404 `page_not_found`. Example `aaNZmyj0mvmWLU`.

## Request body

This operation takes no request body.

### Example request

```bash
curl -X DELETE 'https://secure.yoprint.com/v1/api/store/your-team/setting/group/aaNZmyj0mvmWLU' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Successful response.

Fields:

- `data` (null, required)
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": null,
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
  - When: The API key is missing or wrong. Fix: Send your personal API key as `Authorization: Bearer YOUR_API_KEY`.
- `403` You are not allowed to do this. `api_access_not_in_plan`: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only `{"message": "Insufficient Permission"}`. Other refusals use the error envelope, with `unauthorized` or `user_is_not_authorized`.
  - When: Your permission group lacks Manage Settings. This 403 has a short body, `{"message": "Insufficient Permission"}`, without `success` or `error`. Fix: Ask the team owner to give your permission group Manage Settings.
- `404` Not found. `page_not_found`: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. `code: null`, with a message that starts "No query results for": there is no record with that id.
  - When: No permission group with that id on this team (`error.code` is null and `error.message` starts "No query results"), the id is not one of this team's hash ids, or you are not a member of the team (both `page_not_found`). Fix: Use an `id` from the list operation and check the team slug.
- `422` The request was refused and changed nothing: `validation_failed` lists what to fix in `error.fields`, other codes name a business rule. When the team's plan does not include the feature, the body is only `{"message": "This feature is not available to your team's plan."}`.
  - When: The team's plan doesn't include advanced permission management. The body is short: `{"message": "This feature is not available to your team's plan."}`. Fix: Upgrade the plan.
  - When: The group still has members (`deleting_role_with_active_users_prohibited`). Fix: Move its members to another group with Move a member to a permission group.

## Related

- [Move a member to a permission group](https://developer.yoprint.com/reference/permission-groups/v1-group-change-user-group.md): `PATCH /v1/api/store/{team_slug}/setting/group/{id}/change_user_group`