Page History

...

• Annotate content with Open Graph or other meta tags
• Develop your own custom endpoint that returns JSON in the oEmbed format
• Develop your own custom endpoint that returns JSON in the Ephox Tiny Enhanced Media Embed format

...

As an alternative to including meta tags in your content, you can write a custom API that returns JSON in either the oEmbed or Ephox Tiny Enhanced Media Embed formats.

See the docs on configuring a custom endpoint for details on getting the Enhanced Media Embed server to utilise your custom API.

...

• No room in this spec for multiple embed representations of the same URL
• Must be a separate API rather than just metadata embedded in the content
• Error messages aren’t defined as part of the spec

...

Tiny Enhanced Media Embed endpoint

The other option for developing a custom API endpoint is to return JSON in the Ephox Tiny Enhanced Media Embed format.

...

• Must be a separate API rather than just metadata embedded in the content
• No support from existing plugins
• The Textbox.io editor does not fully take advantage of this format yet

Anchor
ephoxenhancedmediaembedformat ephoxenhancedmediaembedformat

...

Tiny Enhanced Media Embed format

HTTP response status codes

...

• iframely : From Iframely
• opengraph : Generated from Open Graph tags in a resource
• twitter : Retrieved from a Twitter Card
• oembed : Retreived from an oEmbed API
• sm4
• fallback : Ephox Tiny fallback embeds that look at SEO tags and Open Graph tags.
• script_censor : The original embed (from Iframely or oEmbed) had a script in it and has been converted to a summary card.
• smartframe_censor : The original embed had an Iframely smart frame and has been censored into a summary card to avoid a content dependency on Iframely.

...