Attachments

View a list of Pleasant Password Server Features

PUT        <url>/api/v5/rest/attachments/{attachmentId:guid}

Example Request

http://localhost:10000/api/v5/rest/Attachments/ee20446c-3f5e-419b-9d8c-a93600fe401f
{
    "CredentialObjectId": "13caaa57-2186-467e-b107-bc29f8c3533e",
    "AttachmentId": "ee20446c-3f5e-419b-9d8c-a93600fe401f",
    "FileName": "updates3.txt",
    "FileData": "UGFzc01h"
}

Example Response

HTTP 204

The server will respond with a status code indicating whether the attachment was successfully updated or not. If the attachment was successfully updated, the server will return a HTTP 204 status code.

DELETE   <url>/api/v5/rest/attachments/{attachmentId:guid}

Example Request

http://localhost:10000/api/v5/rest/Attachments/ac4c94d8-bec2-4afb-8bfd-a93600fb6e49

Example Response

HTTP 204

The server will respond with a status code indicating whether the attachment was successfully deleted or not. If the attachment was successfully deleted, the server will return a HTTP 204 status code.

Note: The routes containing “entries” or “folders” can be substituted with “credential” and “credentialgroup” respectively. This is to allow reverse compatibility of the API for existing clients.