Open oEmbed API

For your open-source project

oEmbed is a great fit if you need embeds. It is an open standard and many solutions exist. Open-source or commercial ones. Say, Iframely open-source and Iframely hosted, to mention a few 🙂

Since many oEmbed options are available, it will be possible for users of your open-source package to switch between proxy implementations with ease, just by changing API endpoint address. Basically, you don’t limit them if you go with oEmbed. They can even develop their own proxy API and still be connected.

However, you do need a default proxy endpoint to put it in your settings. Here’s what we’ve got to help you out:

>>…. & origin=…

Where url is URL-encoded and origin should contain a string with either your GitHub username or your Twitter @handle (which is perhaps the same for most of you).

More request parameters are available too. See docs (except &iframe=1 parameter, which activates hosted iFrames).

The embed codes will be responsive whenever possible, will cover all our 1600+ domains, and will provide summary cards for articles and general links that do not have native embeds. Plus CORS and JSONP so that you can call API with your JavaScript code.

For your site

If you publish Twitter Cards or Open Graph, Iframely can convert those into oEmbed so that you can easily publish your embeds to developers who auto-discover in oEmbed format.

For it, you just add the following markup into <head> section of your page:

    <link rel="alternate" href="" 
            type="application/json+oembed" />
    <link rel="alternate" href=""

Where url is URL-encoded and origin should contain a string with either your GitHub username or your Twitter @handle (which is perhaps the same for most of you).

Twitter players, photos and Open Graph videos work best. Debug your URLs and whitelist your domain for proper coverage. Otherwise, Iframely will generate a summary card.

Contact us if you need a custom parser for your embeds.


  • This open API endpoint is powered by Iframely cloud and have the same uptime guarantee.
  • In your open-source project, make the endpoint address a config variable so that your users can re-configure it to point to any of oEmbed gateways of their choosing when they start using it.
  • Mention the fact that they need to configure oEmbed API endpoint in your README file or where appropriate.
  • Be nice. We reserve the right to rate-limit or block IP addresses. No rate-limit is there by default (we presume innocence). So,
  • Make sure we can contact you in case of an issue. Based on your origin value, if your GitHub profile doesn’t list an email address, please, consider following Iframely on Twitter so we can send a direct message.
  • If you use API commercially, following us on Twitter is required so we can deliver important updates and reach out in case of a problem.
  • Other standard Iframely terms apply.


Fork this document on GitHub and pull-request with the link to your open-source project to list it here.