====== Updating a Password ====== The update action creates a new revision of a password with an updated set of attributes. **Methods:** PATCH\\ **URL:** /api/1.0/password/update\\ **State:** 200 ===== Arguments ===== * **id: String, Required** * revision: String * **password: String, Required** * **label: String, Required** * username: String * url: String * notes: String * customFields: String * **hash: String, Required** * cseType: String * cseKey: String * folder: String * edited: Integer * hidden: Boolean * favorite: Boolean * tags: array ===== Return ===== * id: String * revision: String ===== Notes ===== * If the password is not editable any change to the encrypted properties, the cseType and the hash will be ignored. * If the password is shared you can only use cse types which support sharing * If the password is shared you can not hide the password * If the password is not hidden and should be moved to a hidden folder, it will be moved to the base folder instead * If the password has tags and you want to remove all tags, you need to submit an array with one invalid tag id * If the folder uuid is invalid or does not exist, the base folder uuid will be used instead * 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 * If the hash has not changed, the edited field from the last revision will be used * If the cseType is set to "none", the hash will be calculated on the server * If the tags argument is empty or missing, no changes will be made * If the tags argument contains invalid tag ids, they will be ignored * You can assign hidden tags to a not hidden password, but they will not be visible. Therefore another client might remove the tag by accident