Released August 4, 2020 | Available until November 1, 2022 | Blog post
Deprecated in v8.0+. Will be deprecated in all versions Nov 2, 2020.
Applies to all versions.
This change applies to all versions.
Newly created apps can now choose an App Type: Business, Gaming, or None. This simplifies the App Review interface by removing inappropriate Permissions and Features based on the chosen type. In addition, apps typed as Business apps use a new authorization mechanism, no longer use modes, and have access to a new Feature. Refer to the Business apps changelog entry for details.
Apps typed as Business apps use a new authorization mechanism called Access Levels. Access Levels replace the functionality provided by Development Mode and Live Mode, which have been removed for Business apps, and make the App Review process simpler and more intuitive. In addition, a new Business Asset User Profile Access Feature has been released, which allows Business apps to read a small set of public User fields. These changes are described in more detail below.
Applies to all versions.
Access Levels are a new Graph API authorization mechanism for Business apps that apply to Permissions and Features on an individual basis. Standard Access only allows access to data owned by users who have a Role on the app, or a Role in a Business that has claimed the app. Advanced Access allows access to data owned by any app user, but requires App Review. Business apps are auto-granted Standard Access for all Permissions and Features available to their type.
Applies to all versions.
Development Mode and Live Mode have been removed for apps typed as Business apps. These modes have been replaced by Access Levels, which provide the same functionality and more versatility — since Business apps have Standard Access for all available Permissions and Features, any user with a Role on the app, or a Role in a Business that has claimed the app, can grant the app any available Permission at any time. This eliminates the need for App Review or having to switch between modes during development.
Applies to all versions.
The new Business Asset User Profile Access Feature allows Business apps to read a small set of public Fields on a User, as long as the User has engaged with assets owned by a Business that has claimed the app. Refer to the Business Asset User Profile Access reference for a list of readable User Fields.
Applies to all versions.
Deprecated in v8.0+. Will be deprecated in all versions Nov 2, 2020.
Deprecated in v8.0+.
GET /{group-id}/posts
Deprecated in v8.0+. Will be deprecated in all versions Nov 2, 2020.
Applies to all versions.
A new GET /instagram_oembed
endpoint has been introduced. It provides the same functionality as Instagram's Legacy oEmbed endpoints, which will be deprecated on Oct 24, 2020. The new endpoint requires an access token, so you will need a Facebook Developer account and registered app to access it. Refer to the Instagram oEmbed document for usage instructions and additional details.
Deprecated in v8.0+.
Deprecated in v8.0+.
Deprecated in v8.0+.
Use the GET /{live-video-id}/reactions
endpoint to get likes for a LiveVideo.
Applies to v8.0+. Will apply to all versions on Nov 2, 2020.
The save_vod
parameter is deprecated for the following edges:
POST /{user_id}/live_videos
POST /{group_id}/live_videos
POST /{page_id}/live_videos
POST /{event_id}/live_videos
Deprecated in v8.0+.
Applies to all versions.
App Review for Messenger has been moved from Products > Messenger > Settings to App Review in the app dashboard. To request Messenger specific permissions, pages_messaging
, pages_user_gender
, pages_user_locale
, and pages_user_timezone
, go to App Review > Permissions and Features. See the Messenger App Review documentation for more details.
Applies to v8.0+.
The nested persistant menu type has been deprecated for POST /{page-id}/messenger_profile
.
Applies to v8.0+.
Support for sending and receiving products on Messenger for Shops. This includes the Product Template that can be used to send products in messages, Webhooks for messages with product template and messages from Facebook Shops Product Detail Page, and echo Webhooks for messages with products.
Deprecated in v8.0+.
Deprecated in v8.0+. Will be deprecated in all versions on Nov 2, 2020.
GET /{open-graph-action-id}/comments
POST /{open-graph-action-id}/comments
Deprecated in v8.0+.
DELETE /{page-id}/tabs
GET /{group-id}/posts
GET /{page-id}/place_topics
GET /{page-about-story-id}
POST /{page-about-story-id}
POST /{page-id}/page_about_story
Deprecated in all versions.
The Page Post comment ID format, {page-id}_{post_id}_{comment-id}
, has been deprecated. Use the {pagepost-id}_{comment-id}
format instead.
Deprecated in all versions.
Deprecated in v8.0+.
Deprecated in v8.0+. Will be deprecated in all versions on Nov 2, 2020.
Use the GET /post/reactions
endpoint to get likes for a post.
Deprecated in v8.0+. Will be deprecated in all versions Nov 2, 2020.
Deprecated in v8.0+. Will be deprecated in all versions on Nov, 2020.
This change will apply to all versions on October 24, 2020.
Facebook oEmbed Endpoints, which allow apps to get embed HTML for public Facebook posts and videos, will be deprecated on October 24, 2020. Three new endpoints have been introduced which provide the same functionality as the old endpoints they are replacing:
The new endpoints require an Access Token and requests will be subject to rate limiting. Please refer to the new oEmbed endpoint documenation for usage details and additional information.
Deprecated in v8.0+.
Deprecated in v8.0+. Will be deprecated in all versions on Nov, 2020.
Deprecated in all versions.
This change applies to all versions.
Starting Oct 24, 2020, the following fields will require Data Access Reauthorization after 90 days of inactivity:
Applies to all versions on Oct 24, 2020.
Starting October 24, 2020, the GET /{user-id}/picture
endpoint (GET /{user-id}?fields=picture
) will require an App-Scoped User ID (ASID) for tokenless requests. If you query the User with a non-ASID, you must include an App, Client, or User Access Token in the request. Refer to the User Picture reference for details.
Deprecated in v8.0+.
Deprecated in v8.0+. Will be deprecated in all versions on Nov 2, 2020.
GET /{company-id}/access_requests
GET /access_requests
Released August 4, 2020 | Available until May 4, 2021 | Blog post
Deprecated in v8.0+.
GET /AdReportSchedule
DELETE act_{ad-account-id}/adsets
Applies to v8.0+. Will apply to all versions on Nov 2, 2020.
Apps need granular permissions to access the business fields of an Ad Account. Permissions should be granted for a specific Business object.
Applies to v8.0+.
All ads using asset_feed_spec
must contain at least two target customization rules. If your creative uses asset_feed_spec
and includes less than two rules, you will not be able to create that ad.
This change affects Placement Asset Customization, Multi-Language Ads, and Segment Asset Customization.
Applies to v8.0+. Will apply to all versions on Nov 2, 2020.
All use cases unrelated to geolocation have been deprecated for Segment Asset Customization users. With this change, all targeting rules must contain geolocation information inside their customization spec. There is an exception for the default rule, which does not need to include geolocation.
Applies to v8.0+
The TARGET_COST
bid strategy is deprecated. To continue controlling cost, we recommend using cost cap bidding. See all available bid strategies.
Deprecated in v8.0+.
GET
{system-user-id}
/updated_by
Applies to all versions
The following endpoints have been reintroduced:
Both endpoints had previously been deprecated with the launch of Graph API V6.0.
/{canvas-id}/collection_hero_image
/{canvas-id}/collection_hero_video
/{canvas-id}/collection_thumbnails
Applies to v8.0+. Will apply to all versions on January 31, 2021.
You no longer need the ads_management
permission to access product catalog endpoints. Moving forward, you will need the catalog_management
permission to call those endpoints. Developers who have had access to catalog endpoints via ads_management
in the last 90 days will be automatically migrated to catalog_management
permissions by August 14, 2020.
From now until February 28, 2021, developers using prior versions of the API are still able to call product catalog endpoints with the ads_management
permission. If you are using v8.0, you must have catalog_management
permission.
After the February deadline, the catalog_management
permission will no longer be associated with ads_management
, so users will have to explicitly grant catalog_management
permission for your app.
Applies to v8.0+. Will apply to all versions on Nov 2, 2020.
[UPDATED] The following Catalog API endpoints now respect two-factor authentication Business settings. Any app calling this endpoint will receive an error if the Business that owns the catalog requires two-factor authentication for the current app user and the app user has not authenticated via two-factor.
When the current app user has access to the catalog through a partner business, we respect the authentication requirements from the partner’s Business Manager. System users do not have to authenticate via two-factor.
POST /{business-id}/owned_product_catalogs
POST /{destination-id}
POST /{home-listing-id}
DELETE /{home-listing-id}
POST /{hotel-id}
DELETE /{hotel-id}
POST /{hotel-id}/hotel_rooms
POST /{hotel-room-id}
DELETE /{hotel-room-id}
POST /{page-id}/product_catalogs
POST /{product-catalog-id}
DELETE /{product-catalog-id}
POST /{product-catalog-id}/agencies
DELETE /{product-catalog-id}/agencies
POST /{product-catalog-id}/assigned_users
DELETE /{product-catalog-id}/assigned_users
POST /{product-catalog-id}/batch
POST /{product-catalog-id}/categories
POST /{product-catalog-id}/destinations
POST /{product-catalog-id}/external_event_sources
DELETE /{product-catalog-id}/external_event_sources
POST /{product-catalog-id}/flights
POST /{product-catalog-id}/home_listings
POST /{product-catalog-id}/hotel_rooms_batch
POST /{product-catalog-id}/hotels
POST /{product-catalog-id}/items_batch
/{product-catalog-id}/pricing_variables_batch
POST /{product-catalog-id}/product_groups
POST /{product-catalog-id}/product_feeds
POST /{product-catalog-id}/product_sets
POST /{product-catalog-id}/products
POST /{product-catalog-id}/vehicles
POST /{product-feed-rule-id}
DELETE /{product-feed-rule-id}
POST /{product-feed-id}
DELETE /{product-feed-id}
POST /{product-feed-id}/rules
POST /{product-feed-id}/uploads
POST /{product-feed-id}/upload_schedules
POST /{product-feed-schedule-id}
DELETE /{product-feed-schedule-id}
POST /{product-feed-upload-id}/error_report
POST /{product-group-id}
DELETE /{product-group-id}
POST /{product-group-id}/products
POST /{product-item-id}
DELETE /{product-item-id}
POST /{product-set-id}
DELETE /{product-set-id}
POST /{vehicle-id}
Applies to v8.0+
GET /{ad-study-id}?fields=split_test_config
GET /{ad-study-id}?fields=iterative_split_test_config
Applies to v8.0+
GET /search?type=adzipcode
ads_management
permission. The new deadline is February 28, 2021.GET /{place-id}
to GET /{place-information-id}
. GET /{place-id}
was not deprecated.