We Really Need a GET Method for Workflow APIs

Hey @gf_wolfer, what you’re asking is right on topic. Rather than write on at length here about the relationship between oEmbed standard and embed.ly and why it’s important and useful today, I’m going to instead point you to THIS really terrific article which explains as well as I could (and also introduces you to all the necessary technical details):


So in my app, my interface does the same thing that you describe. You can configure/customize widget and I serve you up the iFrame code you need to embed. And of course, there’s a “copy to clipboard” button to make that easy. And, I also show you the link to that object on its own page, right?

SO while it is not HARD for a user to take the line or lines of embed code and put them somewhere, the world has MOVED ON from this kind of approach. What is more common now is for a thing that supports embedding to use embed.ly (or sometimes the page’s discoverable oEmbed information) to auto-fetch the necessary embed code and do it FOR YOU.

You see this for example in Squarespace editor. When i was testing my iFrames there, I noticed that you put down an Embed block and it says, “Hey, past the URL of the thing you’re trying to embed and we’ll give it a shot.” And I was like, “Huh, I wonder if that works for MY page?”

Well, of course it doesn’t as I didn’t understand how the auto-embed thing worked. So what squarespace does then is lets you paste in explicit iFrame code, right?

But wouldn’t it just be SO much better if I could tell my users: Hey, I give you the iFrame code here so you can embed this anywhere, but most places on the web you can actually just paste the URL to your calendar page (or booking widget page) and they will auto-magically embed!

That’s what oEmbed / embed.ly can do for you. But as I note there are several blocking issues that can keep you from creating a fully compliant oEmbed API for your app in pure vanilla Bubble.

I’m still obviously working out the minimal easy approach to accomplishing that. However, once I figure it out (meaning that I’ve created an API endpoint that successfully passes embed.ly validation) I will share some info on that here.