OpenGraph.ioOpenGraph.io
Log inStart Free
Embed

oEmbed API for Universal Link Embeds

Generate native oEmbed responses when available and rich fallback embed cards when a URL does not support oEmbed, so your app can embed links, media, articles, and webpages with one API.

Start Free View DocsTry Playground
GETapi.opengraph.io/api/3.0/oembed
url=https://youtube.com/watch?v=dQw4w9WgXcQ
maxwidth=640
Response 200 OK
type“rich”
source“native”
provider_name“YouTube”
width640
height480
html“<iframe src="..." />”
1B+URLs processed
1,000sof developers

Powering link previews, metadata extraction, screenshots, Markdown conversion, embeds, and URL intelligence workflows at scale.

Use cases

Embed links, media, and webpages with one API

The oEmbed API helps developers turn URLs into embeddable content for apps, dashboards, CMS platforms, publishing tools, internal systems, and user-generated content workflows.

Website embedsMedia embedsLink previewsUser-generated contentCMS embedsInternal dashboardsPublishing toolsSocial cardsFallback embed cardsEmbed code generation
API response

Native embeds and fallback cards from one URL

Send a URL and receive embeddable output your application can display, store, or transform into a rich link experience.

Native oEmbed response

Return provider-supported oEmbed data when the URL supports native embeds.

Embed HTML

Use embed-ready HTML when available from supported providers like YouTube, Vimeo, and others.

Fallback embed card

Generate a rich fallback card when a URL does not support native oEmbed.

Title and description

Use page metadata to provide context around the embedded URL.

Preview image

Display a visual thumbnail or preview image alongside the embed when available.

Source indicator

Every response includes a source field (native, discovery, or og_frame) so you know which resolver tier produced the embed.

URL metadata

Use normalized URL data to build consistent embed experiences across providers.

Developer-ready response

Receive structured output that your application can render, save, or pass into other workflows.

API comparison

Choose the right Embed workflow

oEmbed, Embed, and Link Preview can sound similar. Here is how to know which fits your use case.

oEmbed API

Best for oEmbed-compatible workflows

Return native oEmbed data and fallback embed cards from URLs.

Use when:

You need oEmbed-style responses for supported providers, but also want graceful fallback behavior for unsupported URLs.

View oEmbed API

Embed API

Best for universal embeds

Generate embed-ready output across links, media, articles, and webpages.

Use when:

You want a broader embedding workflow that is less tied to the oEmbed format.

View Embed API

Link Preview API

Best for preview cards

Generate rich link previews with title, description, image, domain, and metadata.

Use when:

You need preview cards instead of full embed behavior.

View Link Preview API
Universal coverage

Native oEmbed when possible. Fallback embeds when not.

Standard oEmbed works well when a provider supports it. The problem is that many URLs do not return usable oEmbed data. OpenGraph.io helps fill that gap by generating rich fallback embed cards from metadata, images, and preview data when native oEmbed is not available.

  • Use native oEmbed responses for supported providers
  • Generate fallback embed cards for unsupported URLs
  • Avoid writing provider-specific embed logic
  • Display useful context even when a URL lacks oEmbed support
  • Support media, articles, webpages, and shared links
  • Keep user-submitted URLs from becoming plain, empty links
  • Pair embeds with metadata, previews, and screenshots when needed
Start Free View Docs
youtube.com/watch?v=…
source: native
Provider embedtype: "rich" · html: <iframe …>
example.com/article/…
source: og_frame
Fallback embed cardtype: "hybridEmbed" · OG metadata
Generator vs API

Use a generator for one embed. Use the API for product workflows.

Embed Code Generator

Best for one-off embed creation.

You want to paste a URL and manually generate embed code for a page, article, media item, or website — without writing code.

View Docs

oEmbed API

Best for automated embed workflows.

You need to generate embeds for user-submitted URLs, CMS content, dashboards, publishing tools, internal platforms, or customer-facing products at scale.

Start Free
How it works

From URL to embed in seconds

01

Send a URL

Pass any public URL via path or ?url= query parameter. Optionally set maxwidth and maxheight for layout control.

02

Three-tier resolution

OpenGraph.io checks native oEmbed providers, then oEmbed discovery links, then generates a hosted fallback card. The source field tells you which tier resolved the embed.

03

Receive embed-ready output

Use the html field to render a native embed or fallback card. Structured errors with code and stage when resolution fails.

Resolution tiers

Three paths to an embed, always labeled

Every response includes a source field so you know exactly how the embed was resolved. Broken native providers gracefully degrade to the fallback frame.

source: native

Native provider

The URL matches a known oEmbed provider such as YouTube or Vimeo. The native embed is passed through.

source: discovery

oEmbed discovery

The page advertises an oEmbed endpoint via a discovery link tag. We fetch and return it.

source: og_frame

Hosted fallback frame

No native embed exists. A hosted preview card is generated from the page OpenGraph metadata.

API parameters

oEmbed-compatible options built in

Pass URLs the way that fits your integration. Control sizing. Read structured errors when resolution fails.

url query parameter

Pass the target URL as ?url= instead of a path segment. Easier for demos, migrations, and playground integrations.

maxwidth / maxheight

Standard oEmbed sizing hints forwarded to native providers and applied to fallback frame dimensions.

source field

Responses include source: native | discovery | og_frame so you can label embeds and debug resolution paths.

theme & template

Customize fallback card appearance with theme=light|dark|auto and template=default|compact for card vs banner layouts.

Full API reference
Developer experience

Built for developers embedding user-submitted URLs

Simple API access

Start with an API key and generate embed-ready output from URLs without provider-specific setup.

Native and fallback behavior

Use native oEmbed when available and fallback cards when it is not. One endpoint covers both.

Docs when you need them

Implementation details live in the docs so this page stays focused on product fit.

Free requests to start

Test real URLs before using embeds in production workflows.

Works with user-generated content

Render useful previews for links submitted by users, editors, customers, or internal teams.

Part of URL Intelligence

Pair embeds with previews, metadata, screenshots, extraction, and audits when your workflow needs more context.

Embed family

Build complete link and embed workflows

The oEmbed API is part of OpenGraph.io’s Embed family. Pair embed output with link previews, metadata, screenshots, and optimization tools when your workflow needs more than a native provider embed.

Embed product familyEmbed APIIframely alternativeEmbedly alternativeMigration guideLink Preview APIOpen Graph MetadataWebsite Screenshot APIMeta Tag GeneratorOpen Graph Checker

FAQ

An oEmbed API lets developers send a URL and receive structured embed data that can be used to display embedded content inside an app or website, without writing provider-specific logic.
OpenGraph.io generates a fallback embed card using Open Graph metadata, preview images, and URL data when native oEmbed is not available. This means every public URL gets useful embed output instead of an error.
The oEmbed API is focused on oEmbed-compatible workflows and returns oEmbed 1.0 spec responses. The Embed API is broader and supports more general embedding workflows beyond the oEmbed format.
The oEmbed API returns embed-ready output including native iframe HTML for supported providers. The Link Preview API returns rich preview cards with title, description, image, domain, and metadata, useful for showing link context rather than embedding content.
You can generate embed-ready or fallback output from many public URLs. Native embeds depend on provider support, while fallback cards can display useful context from Open Graph data when native oEmbed is not available.
The API can support automated embed-generation workflows inside your application. An embed code generator is usually for one-off manual embed creation, while this API is designed for products, CMS platforms, and applications that need to handle many URLs programmatically.
Yes. In addition to the path-encoded form (/oembed/{encoded_url}), you can pass the target as ?url=https://example.com. Both forms are supported on v1.1 and v3.0.
Every successful response includes a source field indicating which resolver tier produced the embed: native (known provider), discovery (page-advertised oEmbed link), or og_frame (hosted OpenGraph fallback card).
Full documentation, including request parameters, response schema, fallback behavior, and code examples, is available in the API reference.

Start generating universal link embeds

Use OpenGraph.io to generate native oEmbed responses, fallback embed cards, and embed-ready URL output for apps, CMS platforms, dashboards, and user-generated content workflows.

Start FreeView Docs

No credit card required. Free requests included.