Save uploaded file to existing asset
Be aware that the endpoints described in Step 6 are an Either/Or choice. You should use either the Save as a new asset endpoint to save the uploaded file as a new asset, or the Update existing asset endpoint to update an existing asset with the uploaded file.
Path Parameters
Asset id to which to save the uploaded file.
This id must be in requires Bynder’s 32-character 8-4-4-16 GUID format.
Example:00000000-0000-0000-0000000000000000
Import id of a finalised and processed upload to be saved.
This id must be in requires Bynder’s 32-character 8-4-4-16 GUID format.
Example:00000000-0000-0000-0000000000000000
Body
text/plain
Body
Response
201 application/json
Response
Created
Path Parameters
Body
ApiUploadInitResponse
objectShow Child Parameters
Example:pluploads/api/00000000-0000-0000-0000000000000000/image.jpeg
Show Child Parameters
Example:pluploads/api/00000000-0000-0000-0000000000000000/image.jpeg
ApiV4Upload500Error1
objectExample:Could not complete upload
Example:1
Example:false
ApiV4UploadResponse
objectExample:00000000-0000-0000-0000000000000000
Show Child Parameters
Example:final/2ba07d00-586a-4a44-b13c-c58598cfe828/IMG_1874.JPG
Example:000000000-0000-0000-0000000000000000
Example:s3
Example:final/2ba07d00-586a-4a44-b13c-c58598cfe828/
Only for chunk registration
Example:ok
Example:1
ApiV4UploadResponse1
objectExample:00000000-0000-0000-0000000000000000
Show Child Parameters
Example:final/2ba07d00-586a-4a44-b13c-c58598cfe828/IMG_1874.JPG
Example:000000000-0000-0000-0000000000000000
Example:s3
Example:final/2ba07d00-586a-4a44-b13c-c58598cfe828/
Example:1