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

# supportViewFolderDelete

> Delete a folder from the help desk sidebar, as the folder's Delete does. Its views aren't deleted: each, shared or private, moves to the top level of the sidebar and keeps its place in the order. True if deleted, false if the store has no folder with this id, as each delete that loses a race with another gets. Its name stays taken: a new folder can't reuse it.

**Required scopes:** [`support_config_write`](https://developers.redo.com/docs/api-reference/v3/reference/scopes#scope-support_config_write)

## Arguments

**id** `ID!` *required*

The id of the folder to delete.

## Returns

**supportViewFolderDelete** `Boolean!` *required*

## Errors

Besides the [errors any request can return](https://developers.redo.com/docs/api-reference/v3/errors.md), this operation fails with these codes in `extensions.code`.

| Code | HTTP status | Meaning | Retry |
| - | - | - | - |
| `API_TOKEN_REQUIRED` | `403` | The credential has no API token to attribute the change to, such as a first-party token. Nothing was sent. | Call with a store API token. |
| `BAD_USER_INPUT` | `400` | An argument is invalid, or names something the store doesn't have. The message says which. Nothing was written. | Fix the input the message names, then send it again. |
| `INTERNAL_SERVER_ERROR` | `500` | Something failed on Redo's side. The change may or may not have been made. | Read the record to see whether the change was made before sending it again. A send with an idempotencyKey is safe to retry with the same key. |

## Example

```graphql theme={null}
mutation {
  supportViewFolderDelete(id: "...")
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.