This document explains how to use the new Facebook oEmbed endpoints. These endpoints are replacing the old oEmbed endpoints which are being deprecated on October 24, 2020.

If you are migrating off of the old endpoints, make sure to read this document in its entirety since the endpoint paths and their requirements have changed.

You may receive intermittent HTTP 400 errors from the legacy endpoints that will be deprecated on October 24, 2020. These are part of the internal migration process and can be resolved by retrying your request. More information below.

Facebook oEmbed

Facebook oEmbed endpoints allow you to get embed HTML and basic metadata for pages, posts, and videos in order to display them in another website or app.

Common Uses

  • Rendering Facebook pages, posts, and videos in messaging apps.
  • Embedding Facebook pages, posts, and videos in websites and blogs.
  • Rendering Facebook pages, posts, and videos in a content management system.



GET /oembed_page

Get a Facebook page's embed HTML and basic metadata.

GET /oembed_post

Get a Facebook post's embed HTML and basic metadata.

GET /oembed_video

Get a Facebook video's embed HTML and basic metadata.



Facebook oEmbed endpoints are only meant to be used for embedding Facebook content in websites and apps. They are not to be used for any other purpose. Using metadata and page, post, or video content (or their derivations) from the endpoints for any purpose other than providing a front-end view of the page, post, or video is strictly prohibited. This prohibition encompasses consuming, manipulating, extracting, or persisting the metadata and content, including but not limited to deriving information about pages, posts, and videos from the metadata for analytics purposes.

oEmbed Product

In order to access the endpoint you must add the oEmbed Product to your app. You can do this by signing into the App Dashboard, selecting your app, clicking the Products link, locating oEmbed, and adding the Product.

Access Tokens

The Facebook oEmbed endpoints require either an App Access Token (recommended) or Client Access Token.

App Access Tokens

If your app relies on a backend server, we recommend that you use an App Access Token when accessing the oEmbed endpoint. Rate limits are dependent on the type of token included in the request, and App Token Rate Limits allow for up to 5 million requests per day.

Instructions for generating App Access Tokens can be found in the App Tokens section of our Access Tokens documentation.

Please note that App Access Tokens should never be used client-side. They should always be kept secure and stored on your server. If your app must use a token client-side, use a Client Access Token instead.

Client Access Tokens

If your app must access the oEmbed endpoint from a user agent such as a mobile device or web browser, your app must use a Client Access Token and will be subject to Client Token Rate Limits.

To get a Client Access Token, sign into your App Dashboard and navigate to Settings > Advanced > Security > Client Token.

Unlike App Access Tokens, Client Access Tokens cannot be used in oEmbed endpoint requests on their own, they must be combined with your App ID. To do this, append your token to the end of your App ID, separated by a pipe symbol (|):


For example:


Rate Limits

Rate limits are dependent on the type of Access Token your app includes in each request.

App Token Rate Limits

Apps that rely on App Access Tokens can make up to 5 million requests per 24 hours.

Client Token Rate Limits

Client Token Rate Limits are significantly lower than App Token Rate Limits. We do not reveal the actual limit as it will change depending on your app activity. However, you can safely assume that your app will not reach its limit unless it exhibits bot-like behavior, such as batching thousands of requests, or sending thousands of requests per agent or app user.

Getting Embed HTML

To get a page, post, or video’s embed HTML, send a request to the corresponding page, post, or video oEmbed endpoint:

TargetEndpoint and Query Structure


GET /oembed_page?url={url}&access_token={access-token}


GET /oembed_post?url={url}&access_token={access-token}


GET /oembed_videos?url={url}&access_token={access-token}

Replace {url} with the URL of the page, post, or video you want to query and {access-token} with your App or Client Access Token (or pass it to us in an HTTP header). If you are using a Client Access Token, remember that you must combine it with your App ID using a pipe symbol otherwise the request will fail.

Upon success, the API will respond with a JSON object containing the page, post, or video’s embed HTML and additional data about the page, post, or video. The embed HTML will be assigned to the html property.

Refer to each endpoint’s reference for a list of query string parameters you can include to augment the request. You may also include the fields query string parameter in any request to specify which Fields you want returned. If omitted, all default Fields will be included in the response.

Sample Page Request

curl -i -X GET \

Sample Response

Some values truncated with an ellipsis (...) for readability.

  "provider_url": "",
  "provider_name": "Facebook",
  "height": 500,
  "html": "<div id=\"fb-root\"></div><script async=\"1\" defer=...",
  "type": "rich",
  "version": "1.0",
  "width": 340

URL Formats

The url query string parameter accepts the following URL formats:





By default, the embed HTML contains a reference to the sdk.js JavaScript library. To get embed HTML without the reference so you can load it separately, include the omitscript=true query string parameter.

Passing Access Tokens in a Header

If you don’t want to include your Access Token in your request’s query string, you can pass it to us through an Authorization HTTP header instead.

Authorization: Bearer {access-token}

For example:

curl -i -X GET \
  "" \
  --header "Authorization: Bearer 96481..."