Skip to main content
🔍

DAM Audit Webinar

Learn how to clean, organize, and optimize your DAM portal.

The upload API’s documentation is rather confusing. My team and I are attempting to upload media onto bynder, and we have gotten stuck multiple times. We pulled down the sdk to see how it handles this, and it wasn’t much help.

Biggest problem currently:
Purportedly - when you call the api/v4/upload/{id} route, you should get a return of:

{
"status": "ok",
"output": "final/2ba07d00-586a-4a44-b13c-c58598cfe828/",
"batchId": "00000000-0000-0000-0000000000000000",
"file": {
"bucket": "BUCKET",
"path": "final/2ba07d00-586a-4a44-b13c-c58598cfe828/IMG_1874.JPG",
"type": "s3"
},
"filename": "final/2ba07d00-586a-4a44-b13c-c58598cfe828/IMG_1874.JPG",
"importId": "000000000-0000-0000-0000000000000000",
"locationType": "s3",
"success": 1
}

However - we are getting:

{
"status": "ok"
}

and nothing else. This is bad, because we need the contents of that expected return in order to proceed with the upload process. We have tried multiple different methods and even browsed the old apiary documentation for solutions (by the way, the new docs do not have any of the required information for uploading the files to s3, someone may want to look into that! If it weren’t for the sdk and outdated docs, we would’ve been dead in the water!)

It would be amazing if there was just a simple “upload media” route that we could call once to simplify this like other platforms! If there is something like this and we have somehow missed it, please let me know! Thanks!

Great to see you in the Community ​@JosefBausch, and thanks for sharing your question. I am sorry to hear about your frustrating experience. I’ll pass this along to Support so they can help you troubleshoot further. If we find the articles need an update, I’ll also flag it with the team.


Reply