**Patch: /api/1.0/folder/update**

The update action creates a new revision of a folder with an updated set of attributes.

**Arguments:**
  * **id: The id of the folder**
  * revision: The current revision known to the client. If not the latest revision, the request will fail.
  * **label: The label of the folder**
  * parent: The current parent folder
  * cseType: The client side encryption type
  * cseKey: The UUID of the key used for client side encryption. Required if cseType not "none"
  * edited: Unix timestamp when the user has last renamed the folder
  * hidden: Whether or not the folder should be hidden
  * favorite: Whether or not the user has marked this folder as favorite

**State:**
200

**Return:**
  * id: The UUID of the folder
  * revision: The UUID of the revision

**Notes:**
  * If the uuid of the parent folder is invalid or does not exist, the base folder uuid will be used instead
  * If the folder is not hidden and should be moved to a hidden parent folder, it will be moved to the base folder instead
  * If hou hide a folder, all folders and passwords in it will be hidden as well
  * If you unhide a folder no change to the folders and passwords in it will be made and they will remain hidden
  * If the revision argument is present, the value must match the latest revision or the action will fail with an error. This prevents the client from overwriting a more recent revision on the server with old data.
  * If the edited argument is "0" or missing, the timestamp from the last revision will be used
  * If the edited time is in the future, the current time will be used