Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added sub-codes for 404 responses
Excerpt

Update a media file to in the dialogportal™ Media Archive.

Media in the archive is contained in a folder structure, and file and folder names are unique within their respective folders.

When attempting to create a media file with a name that already exists in the folder, the autoName field is used to determine the correct action. When autoName is omitted or set to false, a 303 response will be returned including a location header containing the URL to the existing media file. When autoName is true, the file will be created with an auto-incremented "index" appended to the file name, "file_1.txt", "file_2.txt" etc.

To add new folders simply include them in your folderPath. Folders that do not already exist will be created.

file content and description properties are updateable. The fileName and folderPath are used to uniquely identify the media file.

Endpoint ID:

9101

Method:

Status
colourGreen
titlePUT

URL:

/content/media

Request body:

JSON data with information about the media to be updated.

Required fields:
 

fileName

A The media file name or title of the media item..

 contentTypeThe content mime-type, i.e. "image/gif" or "text/plain". The contentType should be same as existing file.
Optional fields:
 folderPathA The folder path of the media file to be updated. This path is not the entire URL (which also contains the customer name, fileName etc.) but simply a "/"-delimited string of folder names. Exclude the folderPath to update a file in the root folder.
Optional updatable fields to be updated:
 content

The content, formatted as a base64 encoded text string.

 description

A description that will be displayed in dialogportal™

 contentType

The content mime-type, i.e. "image/gif" or "text/plain".

Code Block
titleExample: Create Update a single pixel image
 {
   "contentfileName": "R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==clear_1x1.gif",
   "contentTypefolderPath": "image/gifassets/generic_images/small",
   "fileNamecontent": "clear 1x1.gifR0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==",
   "folderPathdescription" : "Assets/Generic Images/Small",
   "autoName" : true
}

Response body:

A JSON object containing the url to the newly created content.
Code Block
titleExample
{
  "url": "https://media.dialogportal.com/customer_name/assets/generic_images/small/clear_1x1.This is a media description.",
   "contentType": "image/gif"
}
The URL format is

Response body:

Base URLhttps://media.dialogportal.com/
Customer name
customer_name/
Folder path
assets/generic_images/small/
File nameclear_1x1.gif
Note

The fileName and folderPath have been sanitized, making them safe to use in a URL.

None

Status codes:

201204

Media created successfully.

 303

A media file with this name already exists in the folder.

The response includes a location header containing the URL to the existing media file.

updated successfully

 400.1Content type not recognized
 400.2Media files may not be larger than 2MB
 400.3Content type mismatch
 404.4Media file not found
 404.5Folder not found