I recently embedded Whereby as my video provider and a few users were interested in a tutorial. It is VERY simple. Go over to Embed video calls and video chat API | Whereby Embedded and reach out to set up an account. It is free and easy to set up. Once you have your account, you generate an API key and add your Bubble app’s domain as an “Allowed domain.”
Please note that I set up the API call as an “action” so that I can generate these “meeting rooms” in my workflows. When I set this call up, I used an arbitrary startDate and endDate and it hasn’t caused any issues. The call creates a meeting with unique URLs, one for the host, and one for the attendees. You can set the room settings via your Whereby Embed account.
You can also customize the Whereby “room” by changing the URL for specific settings by following the instructions here:
API Docs can be found here, though I doubt you’ll need them: Whereby
I’m a huge fan of Whereby. Their support has been fantastic, they offer a free trial, pricing is extremely fair, the conferencing has been reliable and honestly has some sweet features. I hope this helps some of you with your video conferencing needs!
@gbenchanoch thank you for the tutorial. I just discovered Whereby today. Correct me if i’m wrong, but their website shows the embedded function as starting at $199 per month with no free option showing on their pricing page. Have I misunderstood something?
It looks like they have changed their base price but are supplying more base minutes per month. I would reach out to inquire, as I built with them about 6 months ago.
@simonpurdon10 - sorry for the delay, haven’t been using Bubble in quite a while. At the time of implementation, I wasn’t as knowledgeable of proper API formatting - so the doubling up of the Authorization header likely wasn’t necessary. I’m sure at the time I was figuring out and got it to work and left it as is.
Regarding the Body - I believe that Bubble Body input fields auto create the JSON object sent out to the API. The Body “text input area” labeled “Body (JSON object, use <> for dynamic values)” is another way to set the JSON object. The difference is that you can set the optionality of certain fields and whether they can be modified in workflows when using the “Private”, “Allow blank”, “Optional” etc. inputs fields. This is how I understand it at least!
Were you able to get Whereby going? If not, feel free to DM me - I’d be glad to help.
