> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nonefivem.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Feature Flag

> Permanently delete a feature flag

Permanently deletes a flag and republishes your configuration without it. The key becomes available for reuse.

<Warning>
  This cannot be undone. If you only want servers to stop seeing the flag, use
  [`PATCH /flags/{flagId}`](/cloud/api-reference/flags/update) with
  `"archived": true` instead — the flag is kept and its key stays reserved.
</Warning>

## Authorization

<ParamField header="Authorization" type="string" required>
  Bearer token for authentication. Format: `Bearer <your-api-key>`
</ParamField>

## Required Permission

`FLAGS_WRITE`

## Path Parameters

<ParamField path="flagId" type="string" required>
  The flag's UUID.
</ParamField>

## Response

<ResponseField name="message" type="string">
  Confirmation message.
</ResponseField>

## Status Codes

| Status | Meaning                           |
| ------ | --------------------------------- |
| `200`  | The flag was deleted              |
| `400`  | `flagId` is not a valid UUID      |
| `401`  | Invalid or missing API key        |
| `403`  | The key lacks `FLAGS_WRITE`       |
| `404`  | No such flag in this organization |

<Note>
  Deleting is deliberately allowed on a **locked** flag — removing one is how you
  get back under your allowance without subscribing again.
</Note>

Servers reading a deleted flag fall back rather than throwing, so deleting one can never crash a running server.

<RequestExample>
  ```bash cURL theme={null}
  curl -X DELETE "https://api.nonefivem.com/cloud/flags/550e8400-e29b-41d4-a716-446655440000" \
    -H "Authorization: Bearer your-api-key"
  ```
</RequestExample>

<ResponseExample>
  ```json Response theme={null}
  {
    "message": "Feature flag deleted successfully"
  }
  ```
</ResponseExample>