---
title: "Update folder"
method: PUT
path: "/v1/folders/{id}"
tags: ["Folders"]
---

# Update folder

`PUT /v1/folders/{id}`

## Request

- Base URL: `https://api.forwardemail.net`
- URL: `https://api.forwardemail.net/v1/folders/{id}`
- Auth: HTTP basic

Update/rename an existing folder. This operation renames the folder to the new path specified in the request body. You can use either the folder's ObjectID or its current path as the identifier. Folders inside it are renamed with it (e.g., 'Work/Clients' becomes 'Jobs/Clients' when 'Work' is renamed to 'Jobs'). INBOX cannot be renamed.

## Path parameters

- `id` string, required

## Request body

- FolderUpdateInput
  - `path` string, required: New folder path/name

## Response `200`

Folder updated successfully

- Folder
  - `id` string, required: Folder ID
  - `path` string, required: Full folder path
  - `name` string, required: Folder name (last part of path)
  - `parent` string, nullable, required: Parent folder path
  - `uid_validity` integer, required: IMAP UID validity
  - `uid_next` integer, required: Next UID value
  - `modify_index` integer, required: Modification index
  - `subscribed` boolean, required: Whether folder is subscribed
  - `flags` string[], required: Folder flags
  - `retention` integer, nullable, required: Message retention period
  - `special_use` string, nullable, required: Special use designation
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required
  - `object` 'folder', required

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `500`: Internal Server Error

---

[API](https://skmtc.dev/forwardemail/apis/forward-email-api.md) · [All operations](https://skmtc.dev/forwardemail/apis/forward-email-api/llms.txt) · [OpenAPI document](https://skmtc.dev/forwardemail/apis/forward-email-api/revisions/ecefab4527f6?raw)