This is the self-hosted version of Iframely's APIs and HTML parsers.
Iframely takes your URL and returns its metadata. If supported on the URL, we'll add HTML of rich media embeds. Think layers, posts, slideshows, surveys, infographics, maps and more.
This package includes specific domain parsers for most popular publishers. YouTube, Facebook, Instagram, Twitter, SoundCloud, Google Maps, TED, Twitch and many more. See /plugins/domains folder. In addition, we cover many domains by whitelisting media through the generic publishing protocols: oEmbed, Open Graph, Twitter Cards and microformats. For the rest of URLs, you'll include have metadata and thumbnail images from those protocols. Use it to create your own URL previews.
Iframely's whitelist file is fetched from our central database. The changes are synced automatically to your instance by default. But you replace that with your own whitelist file. There should be over 1500 domains covered by the central whitelist.
The minimum version of the Node required for Iframely starting from version 2.0.0 is Node 14. Please see migration steps from earlier versions.
To make use of the data, you need to connect to APIs over HTTP. There are two endpoints available. One in oEmbed and one in Iframely API format. The oEmbed endpoint is just an adapter from Iframely to oEmbed spec.
Iframely format mimics the <head> section of the page. It has meta field for data and links array for media.
Both endpoints accept &url= input and provide JSON response. Below are some open responses from our cloud API, so you can see the format:
You can use Iframely can as Node.js library. That's how we use it in the cloud. However, documentation on it is lacking.
Hosted cloud APIs can optionally return Iframely.com-powered iFrame renders in the html field. iFrames deliver all hosted widgets such as cards for URL previews, GIF support, player events, AMP, and others. Our per-URL customization, predictive sizing mechanism for JavaScript-based embeds to minimize the layout shift, lazy-loading, type-based media whitelist and the number of other configurations are only available in the cloud.
This open-source version provides the web parsers only. Iframely cloud use data from those parsers as-is in production. Though the format of API endpoints between the cloud and self-hosted version should match, there might be minor discrepancies.
Finally, there's a number of domain plugins not included in self-hosted version. We seem to have stopped adding new publishers to the open-source. It looks like many of our later providers need quicker turnaround time for updates and fixes. You can extend the self-hosted version with private plugins too.
To get started with the APIs:
- Your API endpoints will be at
{your.server}/iframely?url=and{your.server}/oembed?url= - How to install & configure your Iframely host.
- API in Iframely format
- API in oEmbed format
- About Link Rels, Types and Media Queries in Iframely format (players, thumbnails, app, reader, survey, slideshow, etc)
- META semantics Iframely API scrapes for you.
- Visual debug tool included in the package is at
{your.server}/debug
We put our best effort to maintain Iframely and all its domain parsers. Please, feel free to reach us on Twitter or to submit an issue if you have any suggestions. Our support email is support at iframely.com
Fork and pull-request, if you'd like to add more plugins and/or contribute fixes or improvements. By doing so, you make your work available under the same MIT license.
Please submit your PR against develop branch. This is where everything gets merged before we release it into master.
MIT License. (c) 2012-2022 Itteco Software Corp. Nazar Leush, Ivan Paramonau and the contributors.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent