Upload videos on Vimeo via API

Hey guys ! Hope you’re all doing well,

I’m building an online learning marketplace, and need my users to send videos to my Vimeo account.

I’ve started building it via their API, but I’m struggling.

I’ve seen on this forum, and almost everyone says that the easiest way would be to use the Pull approach of Vimeo’s API. I’d agree, but I have a few limitations for that :cry: 1 - As Bubble’s app storage is fairly limited, I cannot upload videos to my app and then pull them to Vimeo. Because in the event of simultaneous upload of large videos, my app storage wouldn’t be enough.

2 - I’ve tried using a 3rd party storage service (AWS S3, or Digital Ocean Spaces), but I’m struggling big time to setup my AWS S3 since I don’t know anything about it, and couldn’t get the Digital Ocean Spaces API to work…

3 - From a cost POV, it’d be preferable to directly upload videos to Vimeo, without passing through a storage service.

Therefore, my question is :

Did someone manage to use one of the 2 others approach available with Vimeo’s API ?

I’ve started using the form approach, but I find it quite odd. The API calls returns an HTML form with which my users are supposed to upload their video. But in the call, I need to submit the file size.

So my users would have to upload their file twice ? Or is there a way to “transfer” the file from my file uploader to Vimeo’s HTML form ?

I’m lost, please help me :cry:

@adamhholmes I saw on other posts you had some experience with Vimeo API, maybe you have a solution ? (sorry for the savage poke :sweat_smile:)


It’s been a while since I’ve set up any Vimeo integration… so forgive me if I’m a little off on the details…

I agree that the Form approach seems a little strange, which I why, after having spent some time experimenting with it, I decided against it… but it’s worth pointing out that, despite the fact it says you have to include the file size in the initial call to get the form, you actually don’t need to do that at all… it works and uploads the file even if you don’t include the file size in the call (at least it did the last time I was experimenting with it).

But in the end I’ve always stuck using the ‘Pull’ approach (which, at the time at least, was what was recommended to me by both Bubble and by Vimeo), and have not had any issues with it, and it was fairly simple to get working…

I use AWS for the initial upload (using Zeroqode’s ASW upload plugin)… which did take a bit of work to get set up, but once it’s done it works just fine…

Regarding cost, AWS storage is soooooo cheap, it’s almost negligible for us, but to be honest there’s almost no reason to even keep the video in ASW once it’s been pulled into Vimeo… (aside from having a backup), so if you’re really worried about cost you can just delete the file from AWS as soon as it’s pulled into Vimeo.

Another advantage of using the Pull approach with the AWS plugin is that users can upload multiple videos at once, which (at least for our users) is a big plus point…

As I say, they way we’ve got things set up has been working flawlessly for about two years, and we’re totally happy with the UX from our User point of view…

I may revisit this at some point, and have another look to see if there’s a better way, but for the time being, I’d definitely recommend using the Pull approach for ease of setup.

Salut Thomas.

Struggle no more.

This plugin comes with one-click wizard to automatically configure your AWS S3 environment with Bubble :bubbles:

All good !

In the end, I managed to setup my AWS buckets :sweat_smile:

Merci quand même Redvivi ! :grin:

1 Like