Testimonials
What our customers say about Team Password Manager

API: Passwords

Current Team Password Manager version: 14.177.303

API v6

Sections: List passwords | Show a password | List of users who can access a password | Create a password | Update a password | Update security of a password | Update custom fields definitions of a password | Move a password | Copy a password | Duplicate a password | Archive/un-archive a password | Delete a password | Lock a password | Unlock a password | List files of a password | Upload a file to a password


List passwords

These return the passwords that the user has access to. The returned data is the same as in the passwords lists (all active, archived, favorite and search) in the web interface.

GET /passwords.json (active passwords)
GET /passwords/all.json
GET /passwords/archived.json
GET /passwords/favorite.json
GET /passwords/search/urlencoded_string.json (see notes below)

The responses from these requests are paginated and /count.json, /page/num.json and X-Page-Size can be used. See the section on pagination for more information. Example: GET /passwords/page/2.json

If successful, the response code is 200 OK with the results of the call in the response body.

Example response body:

[
    {
        "id": 68,
        "name": "Wordpress admin",
        "project": {
            "id": 18,
            "name": "www.fictionalgadgetsite.com"
        },
        "project_full_path": [
            {
                "id": 6,
                "name": "Internal",
                "archived": false
            },
            {
                "id": 5,
                "name": "Company projects",
                "archived": false
            },
            {
                "id": 18,
                "name": "www.fictionalgadgetsite.com",
                "archived": false
            }
        ],
        "notes_snippet": "Some notes for the wp admin credentials",
        "tags": "wordpress",
        "access_info": "http:\/\/www.fictionalgadgetsite.com\/wp-admin",
        "username": "admin_sg",
        "email": "",
        "has_password": true,
        "strength": "good",
        "expiry_date": "2024-12-31",
        "expiry_status": 3,
        "archived": false,
        "project_archived": false,
        "favorite": false,
        "num_files": 0,
        "locked": false,
        "locking_type": 0,
        "external_sharing": false,
        "linked": false,
        "source_password_id": 0,
        "managed_by": {
            "id": 1
        },
        "created_by": {
            "id": 1
        },
        "created_on": "2024-12-16 14:36:08",
        "updated_by": {
            "id": 1
        },
        "updated_on": "2024-12-16 19:03:34"
    },
    {
        "id": 67,
        "name": "Ftp",
        "project": {
            "id": 18,
            "name": "www.fictionalgadgetsite.com"
        },
        "project_full_path": [
            {
                "id": 6,
                "name": "Internal",
                "archived": false
            },
            {
                "id": 5,
                "name": "Company projects",
                "archived": false
            },
            {
                "id": 18,
                "name": "www.fictionalgadgetsite.com",
                "archived": false
            }
        ],
        "archived": false,
        "project_archived": false,
        "favorite": false,
        "locked": true,
        "locking_type": 1,
        "linked": false,
        "managed_by": {
            "id": 1
        },
        "created_by": {
            "id": 1
        },
        "created_on": "2024-12-16 14:36:08",
        "updated_by": {
            "id": 1
        },
        "updated_on": "2024-12-16 19:02:35"
    },
...
]

Notes:

  • project_full_path shows the path to the project of the password, as seen by the user. It includes the project of the password as the last one. It's the same field as full_path in projects lists.
  • expiry_date uses ISO 8601 format: yyyy-mm-dd.
  • expiry_status has the following values: 0=no date or not expired, 1=expires today, 2=expired, 3=will expire soon.
  • has_password is true if the password entry has the password datum filled in. To view it you need to use the show a password method.
  • strength can have the following values: "" (none), "very weak", "weak", "good" and "strong".
  • Locked passwords (locked=true) will not show any data except id, name, project, archived, project_archived, favorite, locked, locking_type, external sharing, linked and the metadata fields.
  • locking_type has the following values: 0=password not locked, 1=requires a reason to unlock, 2=requires permission to unlock.
  • Linked passwords: linked=true if the password is a linked password, and source_password_id points to the source password.
  • archived=true if the password is archived and/or the project is archived. project_archived=true if the project is archived.
  • Search:
    • You can use the search operators when searching for passwords.
    • You need to urlencode the "urlencoded_string" part.
    • Example (in PHP):
      $search_string = 'username:john'; // Find passwords whose username is "john"
$search_string_urlencoded = urlencode($search_string);
$request_url = 'https://YOUR_TPM_URL/index.php/api/v6/passwords/search/' . $search_string_urlencoded . '.json';

Metadata only lists

All password list requests can include the following header: X-Metadata-Only: true. When this header is used, the response will only include the metadata fields of the passwords. For example:

[
    {
        "id": 68,
        "managed_by": {
            "id": 1
        },
        "created_by": {
            "id": 1
        },
        "created_on": "2024-12-16 14:36:08",
        "updated_by": {
            "id": 1
        },
        "updated_on": "2024-12-16 19:03:34"
    },
    {
        "id": 67,
        "managed_by": {
            "id": 1
        },
        "created_by": {
            "id": 1
        },
        "created_on": "2024-12-16 14:36:08",
        "updated_by": {
            "id": 1
        },
        "updated_on": "2024-12-16 19:02:35"
    },
    ...
]

Metadata only lists are much quicker than the normal lists.

Permissions lists

All password list requests can include the following header: X-Permissions: true. When this header is used, the response will only include the fields that refer to the permissions assigned to users and groups for the password. These fields are: managed_by, users_permissions and groups_permissions. All of these fields are the same fields as in the show a password request, but here only the ids are returned, for speed. The metadata fields are included for completeness. For example:

[
    {
        "id": 68,
        "users_permissions": [
            {
                "user": {
                    "id": 2
                },
                "permission": {
                    "id": 10,
                    "label": "Read"
                }
            },
            {
                "user": {
                    "id": 4
                },
                "permission": {
                    "id": 30,
                    "label": "Manage"
                }
            },
            {
                "user": {
                    "id": 8
                },
                "permission": {
                    "id": 20,
                    "label": "Edit data"
                }
            }
        ],
        "groups_permissions": [
            {
                "group": {
                    "id": 3
                },
                "permission": {
                    "id": 0,
                    "label": "No access"
                }
            }
        ],
        "managed_by": {
            "id": 1
        },
        "created_by": {
            "id": 1
        },
        "created_on": "2024-12-16 14:36:08",
        "updated_by": {
            "id": 1
        },
        "updated_on": "2024-12-16 19:31:06"
    },
    {
        "id": 67,
        "users_permissions": null,
        "groups_permissions": null,
        "managed_by": {
            "id": 1
        },
        "created_by": {
            "id": 1
        },
        "created_on": "2024-12-16 14:36:08",
        "updated_by": {
            "id": 1
        },
        "updated_on": "2024-12-16 19:02:35"
    },
    ...
]

Notes:

  • Requests with the X-Permissions: true header are only available to Admin users.
  • The X-Permissions: true header has priority over the X-Metadata-Only: true header.
  • For locked passwords, users_permissions and groups_permissions are null.

Show a password

This method returns all the data of a password, identified by its internal id.

GET /passwords/ID.json

If successful, the response code is 200 OK with the results of the call in the response body.

Example response body:

{
    "id": 68,
    "name": "Wordpress admin",
    "project": {
        "id": 18,
        "name": "www.fictionalgadgetsite.com"
    },
    "project_full_path": [
        {
            "id": 6,
            "name": "Internal",
            "archived": false
        },
        {
            "id": 5,
            "name": "Company projects",
            "archived": false
        },
        {
            "id": 18,
            "name": "www.fictionalgadgetsite.com",
            "archived": false
        }
    ],
    "tags": "wordpress",
    "access_info": "http:\/\/www.fictionalgadgetsite.com\/wp-admin",
    "username": "admin_sg",
    "email": "",
    "password": "ad$ddgaG8%",
    "strength": "good",
    "time_to_crack": "12 days",
    "expiry_date": "2024-12-31",
    "expiry_status": 3,
    "notes": "Some notes for the wp admin credentials",
    "custom_field1": {
        "type": "Password",
        "label": "root",
        "data": "Qzw-zr$Czj,gL}l",
        "strength": "strong",
        "time_to_crack": "centuries"
    },
    "custom_field2": {
        "type": "One Time Password",
        "label": "2FA",
        "data": "123409"
    },
    "custom_field3": {
        "type": "Date",
        "label": "Renewal",
        "data": "2024-12-31"
    },
    "custom_field4": null,
    "custom_field5": null,
    "custom_field6": null,
    "custom_field7": null,
    "custom_field8": null,
    "custom_field9": null,
    "custom_field10": null,
    "users_permissions": [
        {
            "user": {
                "id": 2,
                "username": "frank",
                "email_address": "frank@teampasswordmanager.com",
                "name": "Frank Steel",
                "role": "Normal user"
            },
            "permission": {
                "id": 10,
                "label": "Read"
            }
        },
        {
            "user": {
                "id": 4,
                "username": "zoe",
                "email_address": "zoe@teampasswordmanager.com",
                "name": "Zoe Timpelton",
                "role": "Normal user"
            },
            "permission": {
                "id": 30,
                "label": "Manage"
            }
        },
        {
            "user": {
                "id": 8,
                "username": "tom",
                "email_address": "tom@teampasswordmanager.com",
                "name": "Tom Landy",
                "role": "Normal user"
            },
            "permission": {
                "id": 20,
                "label": "Edit data"
            }
        }
    ],
    "groups_permissions": [
        {
            "group": {
                "id": 3,
                "name": "External users"
            },
            "permission": {
                "id": 0,
                "label": "No access"
            }
        }
    ],
    "user_permission": {
        "id": 30,
        "label": "Manage"
    },
    "archived": false,
    "project_archived": false,
    "favorite": false,
    "num_files": 0,
    "locked": false,
    "locking_type": 0,
    "locking_request_notify": 0,
    "external_sharing": false,
    "external_url": null,
    "linked": false,
    "source_password_id": 0,
    "managed_by": {
        "id": 1,
        "username": "john",
        "email_address": "john@teampasswordmanager.com",
        "name": "John Boss",
        "role": "Admin"
    },
    "created_on": "2024-12-16 14:36:08",
    "created_by": {
        "id": 1,
        "username": "john",
        "email_address": "john@teampasswordmanager.com",
        "name": "John Boss",
        "role": "Admin"
    },
    "updated_on": "2024-12-17 07:41:13",
    "updated_by": {
        "id": 1,
        "username": "john",
        "email_address": "john@teampasswordmanager.com",
        "name": "John Boss",
        "role": "Admin"
    }
}

Notes:

  • The parents field is no longer available, it has been replaced by project_full_path.
  • project_full_path shows the path to the project of the password, as seen by the user. It includes the project of the password as the last one. It's the same field as full_path in projects lists.
  • expiry_date uses ISO 8601 format: yyyy-mm-dd.
  • Custom fields of type "Date" use ISO 8601 format: yyyy-mm-dd.
  • expiry_status has the following values: 0=no date or not expired, 1=expires today, 2=expired, 3=will expire soon.
  • strength can have the following values: "" (none), "very weak", "weak", "good" and "strong".
  • Locked passwords (locked=true) will not show any data except id, name, project, archived, project_archived, favorite, locked, locking_type, external_sharing, linked and managed/created fields.
  • To view all the data for a locked password, the X-Unlock-Reason header must be supplied with a reason. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.
  • locking_type has the following values: 0=password not locked, 1=requires a reason to unlock, 2=requires permission to unlock.
  • locking_request_notify has the following values: 0=password not locked, 1=notify/request the password manager, 2=notify/request all the users with manage permission.
  • users_permissions is an array of objects of the following data: user object and permission object (permission id, description). Each object describes the permission set to the user on the password. These data are only available to users with manage permission on the password (they're set to null for users that don't have the manage permission).
  • groups_permissions is an array of objects of the following data: group object and permission object (permission id, description). Each object describes the permission set to the group on the password. These data are only available to users with manage permission on the password (they're set to null for users that don't have the manage permission).
  • user_permission is a permission object (permission id, description) that indicates what permission has the user making the request on the password.
  • Linked passwords: linked=true if the password is a linked password, and source_password_id has the id of the source password. Otherwise linked=false and source_password_id=0.
  • archived=true if the password is archived and/or the project is archived. project_archived=true if the project is archived.
  • Custom fields of type "One Time Password" return: in 10.135.236 the secret key in the "data" field and the OTP value at the time of the request in the "otp_value" field, in 10.138.240+ the "otp_value" field does not exist and the "data" field returns the OTP value at the time of the request.

Metadata only

The show a password request can include the following header: X-Metadata-Only: true. When this header is used, the response will only include the metadata fields of the password. For example:

{
    "id": 68,
    "managed_by": {
        "id": 1
    },
    "created_by": {
        "id": 1
    },
    "created_on": "2024-12-16 14:36:08",
    "updated_by": {
        "id": 1
    },
    "updated_on": "2024-12-17 07:47:03"
}

List users who can access a password

This method returns the effective permissions users have on a password. This call shows similar data as the "Security" tab of the password.

GET /passwords/ID/security.json

To use this method with a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.

If successful, the response code is 200 OK with the results of the call in the response body.

This request is only available to the users who have manage permission on the password.

The response is an array of objects that have the following data:

  • User object: data about the user.
  • Permission object: permission id and description.
  • Granted via: how the user is granted the permission on the project.

Example response body:

[
  {
    "user": {
      "id": 2,
      "username": "alan",
      "email_address": "alan@teampasswordmanager.com",
      "name": "Alan",
      "role": "Project manager"
    },
    "permission": {
      "id": 30,
      "label": "Manage"
    },
    "granted_via": "Project: Project manager"
  },
  {
    "user": {
      "id": 4,
      "username": "amy",
      "email_address": "amy@teampasswordmanager.com",
      "name": "Amy",
      "role": "Normal user"
    },
    "permission": {
      "id": 10,
      "label": "Read"
    },
    "granted_via": "Group: SEO"
  },
  {
    "user": {
      "id": 3,
      "username": "ann",
      "email_address": "ann@teampasswordmanager.com",
      "name": "Ann",
      "role": "Normal user"
    },
    "permission": {
      "id": 10,
      "label": "Read"
    },
    "granted_via": "Group: SEO"
  },
  {
    "user": {
      "id": 6,
      "username": "clairewood",
      "email_address": "claire@teampasswordmanager.com",
      "name": "Claire Wood",
      "role": "Normal user"
    },
    "permission": {
      "id": 20,
      "label": "Edit data"
    },
    "granted_via": "User direct"
  },
  {
    "user": {
      "id": 7,
      "username": "janineblack",
      "email_address": "janine@teampasswordmanager.com",
      "name": "Janine Black",
      "role": "Normal user"
    },
    "permission": {
      "id": 0,
      "label": "No access"
    },
    "granted_via": "User direct"
  },
  {
    "user": {
      "id": 1,
      "username": "john",
      "email_address": "john@teampasswordmanager.com",
      "name": "John Boss",
      "role": "Admin"
    },
    "permission": {
      "id": 30,
      "label": "Manage"
    },
    "granted_via": "Password manager"
  }
]

Create a password

POST /passwords.json

The request body must include the data for the password. The required fields are the name and the id of the project the password is to be created in:

{
  "name": "Name of the password",
  "project_id": 21,
  ...
}

If successful, the response code is 201 Created with the internal id of the password in the response body:

{
  "id": 345
}

The following fields can be used when creating a password: 'name' (required), 'project_id' (required), 'tags' (list of comma separated strings), 'access_info', 'username', 'email', 'password', 'expiry_date' (in ISO 8601 format: yyyy-mm-dd, or null or ''), 'notes', 'custom_data1', 'custom_data2', 'custom_data3', 'custom_data4', 'custom_data5', 'custom_data6', 'custom_data7', 'custom_data8', 'custom_data9', 'custom_data10'.

Notes:

  • Custom data fields are allowed even if custom fields are not defined (their type is text by default).
  • The data for custom data fields of type "One Time Password" must be the secret key.
  • The data for custom data fields of type "Date" must be the specified in ISO 8601 format: yyyy-mm-dd.

Update a password

PUT /passwords/ID.json

The request body must include the data for the password. Only the fields that are included are updated, the other fields are left unchanged:

{
  "name": "Changed name of the password",
  "tags": "tag1,tag2,tag3",
  ...
}

If successful, the response code is 204 No content and the response body is empty.

The following fields can be used when updating a password: 'name', 'tags' (list of comma separated strings), 'access_info', 'username', 'email', 'password', 'expiry_date' (in ISO 8601 format: yyyy-mm-dd, or null or ''), 'notes', 'custom_data1', 'custom_data2', 'custom_data3', 'custom_data4', 'custom_data5', 'custom_data6', 'custom_data7', 'custom_data8', 'custom_data9', 'custom_data10'.

Notes:

  • The 'name', if present, cannot be empty.
  • Custom data fields are allowed even if custom fields are not defined (their type is text by default).
  • The data for custom data fields of type "One Time Password" must be the secret key.
  • The data for custom data fields of type "Date" must be the specified in ISO 8601 format: yyyy-mm-dd.
  • To update a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.
  • Linked passwords cannot be updated (they're read only). If you try to update a linked password you'll get a 403 Forbidden response.

Update the security of a password

PUT /passwords/ID/security.json

The request body must include the data for the password:

  • managed_by is the main manager of the password. If present, cannot be 0.
  • users_permissions is an array of [user_id, permission_id]. User permissions will be set for the users passed, deleting the current permissions. permission_id can be: 0=no acces, 10=read, 20=edit data, 30=manage (only 0, 10 for users with role read only). If you want to set "Do not set", simply exclude the user. Admin users, the project manager(s) and the password manager can be included in this list, but it will have no effect. For Read only users these are the only valid permissions: 0, 10.
  • groups_permissions is an array of [group_id, permission_id]. Groups permissions will be set for the groups passed, deleting the current permissions. permission_id can be: 0=no acces, 10=read, 20=edit data, 30=manage. If you want to set "Do not set", simply exclude the group from the list.

Note: you cannot assign the "20=edit data" permission to linked passwords as they're read only. You'll get a 409 Conflict response if you try to do so.

Example of a request body:

{
  "managed_by": 1,
  "users_permissions": [ [2,10],[3,20] ],
  "groups_permissions": [ [1,20] ]
}

If successful, the response code is 204 No content and the response body is empty.

To update the security of a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.

To get the users in your Team Password Manager installation you can use GET /users.json and the groups GET /groups.json.


Update custom fields definitions of a password

PUT /passwords/ID/custom_fields.json

The request body must include the data for the password. Only the fields that are included are updated, the other fields are left unchanged:

{
  "custom_label1": "MySQL user",
  "custom_type1": "text",
  "custom_label2": "MySQL password",
  "custom_type2": "password",
  ...
}

If successful, the response code is 204 No content and the response body is empty.

The following fields can be used when updating a password's custom fields definitions: custom_labelX, custom_typeX (X=1..10).

Allowed custom types (case insensitive): 'Text', 'Encrypted text', 'E-mail' or 'email, 'Password', 'Notes', 'Encrypted notes', "One Time Password" or "OTP" and "Date".

Notes:

  • To delete the definition of a custom field set custom_typeX to an empty string.
  • Deleting the definition of a custom field doesn't delete its data, but it may uncrypt it.
  • No data is passed here, only definition.
  • To update the custom field definitions of a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a 409 Conflict error will be returned.
  • Custom field definitions of linked passwords cannot be updated (they're read only). If you try to update the custom field definition of a linked password you'll get a 403 Forbidden response.

Move a password

Move a password to another project.

PUT /passwords/ID/move.json

The request body must include the ID of the target project:

{
  "project_id": 123
}

If successful, the response code is 204 No content and the response body is empty.

Notes:

  • project_id cannot be 0 or negative.
  • Linked passwords cannot be moved.
  • To move a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.

Copy a password

Copy a password to another project.

POST /passwords/ID/copy.json

The request body must include the ID of the target project:

{
  "project_id": 123
}

If successful, the response code is 201 Created with the internal id of the created password in the response body:

{
  "id": 70
}

Notes:

  • project_id cannot be 0 or negative.
  • Linked passwords cannot be copied.
  • To copy a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.

Duplicate a password

Duplicate a password in the same project.

POST /passwords/ID/duplicate.json

The request body must include the name of the new password:

{
  "new_name": "New Wordpress admin"
}

If successful, the response code is 201 Created with the internal id of the created password in the response body:

{
  "id": 71
}

Notes:

  • Duplicated passwords include the files, have the same passwords and custom fields.
  • new_name cannot be empty.
  • Linked passwords cannot be duplicated.
  • To duplicate a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.

Archive/un-archive a password

PUT /passwords/ID/archive.json

PUT /passwords/ID/unarchive.json

If successful, the response code is 204 No content and the response body is empty.

To archive/un-archive a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.


Delete a password

DELETE /passwords/ID.json

This deletes the password, its files, etc.

If successful, the response code is 204 No content and the response body is empty.

To delete a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.

Notes:

  • linked passwords cannot be deleted (they're read only). If you try to delete a linked password you'll get a 403 Forbidden response.
  • Since v. 12.143.260, the password is moved to the Trash Bin.

Lock a password

PUT /passwords/ID/lock.json

This sets the locking status of a password to locked. From this moment on, any user who wants to use it will have to supply a reason to unlock it.

If successful, the response code is 204 No content and the response body is empty.


Unlock a password

PUT /passwords/ID/unlock.json

This sets the locking status of a password to unlocked.

If successful, the response code is 204 No content and the response body is empty.

To unlock a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.


List files of a password

This method returns the files uploaded to a password. This call shows similar data as the "Files" tab of the password.

GET /passwords/ID/files.json

To use this method with a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.

The response from this request is paginated and /count.json, /page/num.json and X-Page-Size can be used. See the section on pagination for more information. Example: GET /passwords/ID/files/page/2.json

If successful, the response code is 200 OK with the results of the call in the response body.

The response is an array of objects that have the following data: id (each file has a unique id in Team Password Manager, which you can see by clicking on the "Info" button of the file), filename, size in bytes and as it appears in the UI, a snippet of the notes if the file has them and when it was last updated.

Example response body:

[
  {
        "id": 5,
        "filename": "mustang.jpeg",
        "size_bytes": 2868081,
        "size_txt": "2.74 mb",
        "notes_snippet": "Great car",
        "uploaded_by": {
            "id": 1
        },
        "uploaded_on": "2024-12-18 06:47:03",
        "notes_updated_by": {
            "id": 1
        },
        "notes_updated_on": "2024-12-18 06:47:23"
    },
    {
        "id": 3,
        "filename": "server_specs.pdf",
        "size_bytes": 70337,
        "size_txt": "68.69 kb",
        "notes_snippet": "VPS...",
        "uploaded_by": {
            "id": 1
        },
        "uploaded_on": "2024-12-18 06:46:00",
        "notes_updated_by": {
            "id": 1
        },
        "notes_updated_on": "2024-12-18 06:46:00"
    }
]

Metadata only list

This list files of a password request can include the following header: X-Metadata-Only: true. When this header is used, the response will only include the metadata fields of the files. For example:

[
    {
        "id": 5,
        "uploaded_by": {
            "id": 1
        },
        "uploaded_on": "2024-12-18 06:47:03",
        "notes_updated_by": {
            "id": 1
        },
        "notes_updated_on": "2024-12-18 06:47:23"
    },
    {
        "id": 3,
        "uploaded_by": {
            "id": 1
        },
        "uploaded_on": "2024-12-18 06:46:00",
        "notes_updated_by": {
            "id": 1
        },
        "notes_updated_on": "2024-12-18 06:46:00"
    }
]

Upload a file to a password

This method uploads a file to a password.

POST /passwords/ID/upload.json

The request body must include the data for the file, which consists of three fields:

  • file_data_base64 contents of the file. It must be Base64 encoded. This field is required.
  • file_name name of the file. This field is required.
  • notes notes of the file. This field is optional.

Example request body:

{
  "file_data_base64": "dGhpcyBpcyBhIHNpbXBsZSB0ZXh0IGZpbGU=", (Base64 encoded content of the file to upload)
  "file_name": "file_to_upload.pdf",
  "notes": "some notes for the file"
}

If successful, the response code is 201 Created with the internal id of the file in the response body:

{
  "id": 373
}

To use this method with a locked password, the X-Unlock-Reason header must be supplied with a reason, otherwise the response code 403 Forbidden will be returned. When a locked password is accessed with the X-Unlock-Reason, a notification will be sent to the password manager with the supplied reason. Note that locked passwords that require permission to be unlocked cannot be used with the API, and if in this case and the X-Unlock-Reason header is provided a "409 Conflict" error will be returned.


Upload a file to a password example in PHP

The following script shows you how to upload a file to a password using PHP. To run it, save it to a PHP file and replace the variables on top with your own values:

<?php
  // API URL
  $tpm_base_url  = 'https://YOUR_TPM_URL/index.php/api/v6';

  // User with Edit data / Manage permission on the password to upload the file to
  $username = 'YOUR_TPM_USERNAME';
  $password = 'YOUR_TPM_PASSWORD';

  // Password id of the password to upload the file to
  $pwd_id = YOUR_PWD_ID; // For example: 344

  // File to upload, in the same folder as this script
  $file_to_upload = 'YOUR_FILE_NAME'; // For example: 'server_specs.pdf'

  // Read the file, encode it with Base64 and store it in $file
  $file = base64_encode(file_get_contents($file_to_upload));
  if ( $file ) {
    // Method to upload
    $request_uri = '/passwords/' . $pwd_id . '/upload.json';

    // Body with the data to upload the file (JSON encoded array)
    $request_body_json = json_encode(array(
      'file_data_base64' => $file,
      'file_name' => $file_to_upload, // Just the name of the file, do not include the path here
      'notes' => 'Some notes'
    ));

    // Headers: JSON and UTF-8
    $headers = array(
      'Content-Type: application/json; charset=utf-8'
    );

    // POST request
    $ch = curl_init($tpm_base_url . $request_uri);
    curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
    curl_setopt($ch, CURLOPT_HEADER, FALSE); // Does not include header in the output
    curl_setopt($ch, CURLOPT_POST, TRUE);
    curl_setopt($ch, CURLOPT_POSTFIELDS, $request_body_json);
    curl_setopt($ch, CURLOPT_USERPWD, $username . ":" . $password); // HTTP Basic Authentication
    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
    
    // Execute
    $result = curl_exec($ch); 
    $status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);
    
    // Show response
    echo 'Status: ' . $status . '<br/>';
    echo $result;

  } else {
    echo 'Incorrect file';
  }

If successful, the result should show something like this, where "id" is the id of the newly created file:

Status: 201
{"id":380}

Document changelog

Dec 19, 2024: Document created from API v5
Check the API changelog for changes
Questions or Problems? Please contact our support department