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 createdfile content
and description
properties are updateable. The fileName
and folderPath
are used to uniquely identify the media file.
Endpoint ID: | 9101 | |||||||||||||||||||||||||||||||||
Method: |
| |||||||||||||||||||||||||||||||||
URL: | /content/media | |||||||||||||||||||||||||||||||||
Request body: | JSON data with information about the media to be updated.
| |||||||||||||||||||||||||||||||||
Response body: | A JSON object containing the url to the updated content.
The URL format is:
Note | 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 alocation header containing the URL to the existing media file.updated successfully | ||||||||||||||||||||||||||||||
400.1 | Content type not recognized | |||||||||||||||||||||||||||||||||
400.2 | Media files may not be larger than 2MB | |||||||||||||||||||||||||||||||||
400.3 | Content type mismatch | |||||||||||||||||||||||||||||||||
404.4 | Media file not found | |||||||||||||||||||||||||||||||||
404.5 | Folder not found |