Let’s connect
If you know where you are heading to, use links to the left. Otherwise, read on.
This introduction gives the same links in proper context.
Basic flow
Iframely takes your URL as an input, fetches its semantics from the origin server and tries to return rich media embed codes and other URL data.
If successful, you’ll get html as embed code that follows your API settings and optional query-string parameters.
If the request fails, you’ll get an error code and a message.
API endpoint
Iframely API follows JSON format. There are (just) two API endpoints available: one follows oEmbed spec, another provides detailed Iframely data.
Think of it as the <head> of the origin URL with <meta> and media <link>s.
oEmbed is excellent for simple embedding. Iframely data brings more URL meta and details about rich media types & feature flags.
Embed.js lets you use Iframely without API calls.
What URLs to send
We suggest you send everything you have. Iframely knows rich media from over 1900 domains but recognizes thousands more. We offer that you control what you get by allowing rich media types.
What to expect as output
Rich media from third-party publishers comes in a variety of types. Many rich media embeds can be used as-is. Some may require an Iframely-hosted iFrame helper to display correctly. For example, React does not add third-party scripts, and you will need to omit scripts.
Hosted iFrames deliver Iframely interactives such as summary cards, click-to-play and player events.
Customize & fine-tune
You can control every aspect of Iframely via your