Graph API

Released October 8, 2025 | Available until TBD | Blog post

Certificate Transparency

Certificate Transparency has been deprecated. All certificate transparency related endpoints and webhooks have been removed for v24.0+.
For v23.0 and older, GET requests will return static data, POST requests will be rejected, and certificate transparency related webhooks will no longer be sent.
On October 17, 2025, all certificate transparency related endpoints and webhooks will be remove, for all versions.

Live Video API

The overlay_url field on the GET / endpoint has been removed for v24.0+. It will continue to return null for v23.0 and older requests. This field was used to store the URL of live video overlay assets, but the overlay feature was removed from Facebook Live Producer in 2022.

WhatsApp Business Platform

See the WhatsApp Business Platform changelog.

Marketing API

Released October 8, 2025 | Available until TBD | Blog post

Ad Creative

Website destination optimization
Applies to v24.0+.
When you optimize your website destination, you allow Meta to determine which landing page on your website to send a customer to based on which URL we believe is most likely to result in a conversion. Using Optimize website destination means we may direct a customer to a page on your website that's most relevant to them, like your homepage, product page, collection page or another page on your website depending on where they're likely to convert.
The following endpoints are affected:

• POST /{ad-account-id}/adcreatives
• GET /{ad-creative-id}/?fields=destination_spec

Ads that Click to Messenger

Messenger ads for leads deprecation
Applies to v24.0+.
The ability to create lead ads that generate leads in Messenger with the API is being deprecated. You will still be able to create Messenger ads for leads using Ads Manager.
The following endpoints are affected:

• POST /{page-id}/messenger_lead_forms
• POST /{ad-account-id}/adcreatives
• GET /{messenger-lead-gen-template-id}

Advantage+ Campaigns

Advantage+ shopping campaigns and Advantage+ app campaigns deprecation
Applies to v24.0+.
We are introducing a new, unified, and streamlined process for creating campaigns that will replace the existing workflows.
Beginning with v24.0, creation, duplication, and updates to Advantage+ shopping campaigns and Advantage+ app campaigns will no longer be allowed.
Refer to the Advantage+ Campaigns documentation to learn how to migrate your campaigns, or create new Advantage+ campaigns to avoid disruption.
The following endpoints are affected:

• POST /{ad-account-id}/campaigns
• POST /{campaign-id}/copies

Audiences

Customer file custom audiences
Applies to v24.0+. Will apply to all versions January 6, 2026.
Updating customer file custom audiences that are flagged custom audiences will fail. Creating and updating lookalike audiences using flagged seed audiences will fail.
More information on this update and how to resolve flagged custom audiences can be found here.
The following endopints are affected:

• POST {ad-account-id}/customaudiences
• GET {custom-audience-id}
• POST {custom-audience-id}
• POST {custom-audience-id}/users
• POST {custom-audience-id}/usersreplace
• DELETE {custom-audience-id}/users

Lookalike audience field type enforcement

Applies to v24.0+. Will apply to all versions January 6, 2026.
When creating new lookalike audiences, the lookalike_spec field is now required to match the valid types. Requests with a lookalike_spec field containing invalid subfields may fail to create a new lookalike audience.
The following endpoints are affected:

• POST /{ad-account-id}/customaudiences

Budgeting

Ad set budget sharing field conditionally required
Applies to v24.0+.
Ad set budget sharing allows you to share up to 20% of your budget with other ad sets in the same campaign. This is designed to improve performance for campaigns that are not using a campaign budget.
Beginning with v24.0, the is_adset_budget_sharing_enabled field is now required if you are planning to set a budget at the ad set level. Setting it to true is recommended in order to turn on this optimization.
The following endpoints are affected:

• POST /{ad-account-id}/campaigns

Increasing daily budget flexibility

Applies to v24.0+.
Daily budget flexibility is increasing from 25% to 75%. This means up to 75% over your daily budget may be spent on days when better opportunities are available, and less on others.
Your daily budget is used as an average over a seven-day calendar week from Sunday through Saturday. Your weekly spend will not change, and will not be greater than 7 times your daily budget.
The following endpoints are affected:

• POST /{ad-account-id}/adsets
• POST /{ad-account-id}/campaigns
• POST /{ad-set-id}
• POST /{campaign-id}

Conversions

Custom conversions
Applies to v24.0+. Will apply to all versions January 6, 2026.
Updating custom conversions that are flagged custom conversions will fail.
More information on this update and how to resolve flagged custom conversions can be found here.
The following endpoint is affected:

• POST /{custom-conversion-id}

Campaigns

Campaign restrictions for custom conversions and audiences
Applies to v24.0+. Will apply to all versions January 6, 2026.
Creating and updating campaigns that are using flagged custom conversions or audiences will fail.
More information on this update and how to resolve flagged custom conversions and audiences can be found here.
The following endpoints are affected:

• POST /{ad-set-id}
• POST /{ad-account-id}/adsets

Catalog

New batch API payload request limit
Applies to v24.0+.
We’ve added a new limit to the size of request payloads for the Catalog Items Batch API. Starting with v24.0, payload requests will be limited to 30 MB. Note that in terms of the number of items per request, the current limit of 5,000 items remains unchanged.
The following endpoint is affected:

• POST /{product-catalog-id}/items_batch

Product Item endpoint supports allow_upsert
Product Item endpoint supports allow_upsert
Applies to v24.0+.
The allow_upsert flag is now supported for the Product Item POST endpoint. That means users can now not only create product items using the Product Item POST endpoint, but also update existing items.
The following endpoint is affected:

• POST /{product-catalog-id}/products

Placements

Advantage+ placements limited spend
Applies to v24.0+.
This update allows you to allocate up to 5% of your spend to specific placements you would otherwise exclude when it's likely to improve performance.
During ad set creation, you can now apply a limited spend using the new placement_soft_opt_out parameter. There is no change in how placements are fully opted out with Placement Targeting.
Note: This feature works with the Sales and Leads objectives.
The following endpoints are affected:

• POST /{ad-account-id}/adsets
• POST /{ad-set-id}
• GET /{ad-set-id}?fields=placement_soft_opt_out

Facebook video feeds ads placement deprecation

Applies to v24.0+.
Delivery of Facebook video feeds ad placements will be stopped and campaign spending will be shifted to other placements automatically. Attempting to create or update an ad campaign with the Facebook video feeds ad placement will produce an error.
The Facebook Reels placement is the recommended replacement.
The following endpoints are affected:

• POST /{ad-account-id}/adsets
• POST /{ad-set-id}

Targeting

Detailed targeting
Applies to v24.0+. Will apply to all versions January 6, 2026.
We are combining some of the interests currently available in Detailed Targeting into relevant groupings.
Certain detailed targeting interest options will not be supported for new campaigns. When creating new or updating existing campaigns with affected interest options, you will encounter an error preventing you from publishing your changes. If an interest option has been combined, the search results will show the new, consolidated option.
Ad campaigns created before October 8, 2025 can continue to run, but will stop being delivered by January 15, 2026, unless removed or updated with suggested combined options.
Beginning October 8, 2025, duplicated campaigns using the affected interest options will automatically be replaced with suggested combined options for Marketing API v24.0 calls.
The following endpoints are affected:

• POST /{ad-account-id}/adsets
• POST /{ad-set-id}
• POST /{ad-set-id}/copies
• GET /{ad-account-id}/delivery_estimate
• GET /{ad-set-id}/delivery_estimate
• GET /{ad-account-id}/reachestimate
• GET /{ad-account-id}/targetingsearch
• GET /{ad-account-id}/targetingsuggestions
• GET /{ad-account-id}/targetingvalidation
• GET /search

Original source

Graph API

Released May 29, 2025 | Available until TBD | Blog post

WhatsApp Business Platform

• Added a new Cloud API error code for help diagnosing messaging errors. See WhatsApp Business platform changelog.
• Added four new Marketing Messages Lite API error codes for help diagnosing messaging errors. See Marketing Messages Lite API changelog.

Marketing API

Released May 29, 2025 | Available until June 9, 2026 | Blog post

Ad Campaigns

Advantage+ Shopping Campaigns and Advantage+ App Campaigns
Applies to v23.0.+ Will apply to all versions with the release of v25.0.
The advantage_state field in advantage_state_info is a read-only field that indicates if a campaign has reached an optimal level of automation. Beginning with v25.0, the smart_promotion_type field will no longer be available for creating ad campaigns.
The following endpoints are affected:

• GET /{ad-campaign-id}
• GET /{ad-account-id}/campaigns

Audiences

Advanced Targeting

Applies to v23.0+.
Age range and gender settings can now be used as suggestions in ad sets using individual_setting's age and gender parameters inside targeting_automation.
Note: When using suggestions, your ads will reach people outside of the setting when it's likely to improve performance of the ads.
The following endpoints are affected:

• GET /{ad-account-id}/delivery_estimate
• POST /{ad-account-id}/adsets
• POST /{adset-id}
• POST /{adset-id}/copies

Advantage+ Audience

Applies to v23.0+.
Ad sets are now opted-in to Advantage+ audience by default if you're using the default or relaxed setup. You can opt-out in the audience settings when creating or updating an ad set.
This behavior applies only when creating a new ad set; updating an existing ad set will not exhibit this behavior on any version.
The following endpoints are affected:

• GET /{ad-account-id}/delivery_estimate
• POST /{ad-account-id}/adsets
• POST /{adset-id}
• POST /{adset-id}/copies

Bidding

Reservation

Applies to v23.0+.
Beginning with v23.0, the instagram_destination_id field will return the ig_user_id rather than the instagram_actor_id. The instagram_actor_id is also no longer supported in the destination_ids parameter; update your API calls to use the ig_user_id instead.
The following endpoints are affected:

• GET /{rf-prediction-id}
• GET /{ad-account-id}/reachfrequencypredictions
• POST /{ad-account-id}/reachfrequencypredictions

Product Item Videos

Applies to v23.0+.
The videos field has been added to allow for querying of the properties of videos associated with product items.
The following endpoints are affected:

• GET /{product-item-id}

Special Ad Catagories

Ad Sets for Special Ad Category Campaigns

Applies to v23.0. Will Apply to all versions August 27, 2025.
The is_sac_cfca_terms_certified field should no longer be added to an ad set as the rollout of these requirements will not proceed.
The following endpoints are affected:

• POST /{ad-account-id}/adsets
• POST /{ad_set_id}

Custom Audiences

Applies to v23.0. Will Apply to all versions August 27, 2025.
The is_eligible_for_sac_campaigns field should no longer be added to an ad set as the rollout of these requirements will not proceed.
The following endpoints are affected:

• GET /{custom_audience_id}

Original source

Version 22.0

Graph API

Released January 21, 2025 | Available until TBD | Blog post

Instagram Platform

Insights APIs

Applies to all versions.
Insights APIs for both media and user objects are now available for apps that have implemented Instagram API with Instagram Login.
Insights metrics
Introducing the following metrics field for media and user insights:

• views

Metric Deprecations
Applies to v22.0+. Will apply to all versions April 21, 2025.

• clips_replays_count on media insights
• ig_reels_aggregated_all_plays_count on media insights
• impressions on media and user insights
• plays on media insights

Note: API requests with the impressions metric will continue to return data for media created on or before July 1, 2024 for v21.0 and older. API requests made after April 21, 2025 for media created on or after July 2, 2024 will return an error.

v1.0 Endpoint Deprecations

Applies to v22.0+. Will apply to all versions April 21, 2025 May 20, 2025.
The Instagram v1.0 API is deprecated.
The following endpoints are affected:

• GET /{instagram-user-id}
• GET /{instagram-user-id}/agencies
• GET /{instagram-user-id}/upcoming-events
• GET /{instagram-user-id}/authorized-adaccounts
• POST /{instagram-user-id}/upcoming-events
• POST /{instagram-user-id}/authorized-adaccounts
• GET /{instagram-media-id}
• GET /{instagram-media-id}/comments
• GET /{instagram-carousel-id}
• GET /{instagram-carousel-id}/comments
• GET /{instagram-comment-id}
• GET /{instagram-comment-id}/replies
• POST /{instagram-media-id}/comments
• POST /{instagram-carousel-id}/comments
• POST /{instagram-comment-id}/replies
• POST /{instagram-comment-id}
• DELETE /{instagram-comment-id}
• GET /{page-id}/instagram-accounts
• GET /{page-id}/page-backed-instagram-accounts
• GET /{business-id}/owned-instagram-accounts
• GET /{business-id}/instagram-accounts
• GET /{business-asset-group-id}/contained-instagram-accounts
• GET /{fb-business-user-id}/assigned-instagram-accounts
• GET /{fb-user-id}/assigned-instagram-accounts
• GET /{fb-system-user-id}/assigned-instagram-accounts
• GET /{ad account id}/instagram-accounts
• GET /{ad account id}/connected-instagram-accounts-with-iabp
• POST /{page-id}/page-backed-instagram-accounts
• DELETE /{business-id}/instagram-accounts
  Please migrate your API calls to the Instagram Platform endpoints.

Pages

Applies to v22.0+.
Page recommendations have been deprecated for v22.0 and future versions. Attempting to read a recommendation, or get recommendations on a page, will return error code 12, and Page ratings webhooks will no longer be sent.
Affected endoints:

• GET //ratings
• GET /
  Affected webhooks:
• Page ratings

Marketing API

Released January 21, 2025 | Available until February 10, 2026 | Blog post

Ad Creatives

Applies to v22.0+. Will apply to all versions September 9, 2025.
Field Deprecations
The instagram_actor_id field for the following endpoints is deprecated:

• POST /{ad-account-id}/adcreatives
• POST /{ad-account-id}/ads
• POST /{ads-id}
• POST /{ad-account-id}/asyncadrequestsets
• GET /{ad-account_id}/generatepreviews
• GET /generatepreviews
• GET /adcreative
• GET /adcreative/object_story_spec
  Please migrate your API calls to use the new instagram_user_id field.
  The effective_instagram_story_id field has been deprecated for the GET /adcreative endpoint. Use the effective_instagram_media_id field instead.
  The instagram_story_id field has been deprecated for the GET /adcreative endpoint. Use the source_instagram_media_id field instead.

Advantage+ Creative

Standard Enhancements

Applies to v22.0+.
Opting ads in to and previewing ads using the STANDARD_ENHANCEMENTS bundle is no longer supported.
The following endpoints are affected:

• POST /{ad-account-id}/adcreatives
• POST /{ad-account-id}/ads
• GET /{ad-id}/previews
• GET /{ad-account-id}/generatepreviews

Asset Feed Spec

Segment Asset Customization

Applies to v22.0+.
Segment Asset Customization is no longer supported.

Audiences

Detailed Targeting - Employer Exclusions

Applies to all versions.
An employer exclusion can now be created at the ad account level, which will be applied to all active campaigns.
The following endpoints are affected:

• POST /{ad-account-id}/account_controls
• GET /{ad-account-id}/account_controls

Detailed Targeting - Exclusions

Applies to v22.0+. Will apply to all versions April 21, 2025.

• When creating or updating an ad set, an error message will be shown when adding any new detailed targeting exclusions that are not within audience control exclusions at the account level.
• When duplicating an ad set, detailed targeting exclusions (except audience control exclusions at the account level) will be removed in the new campaign.
• When trying to get a delivery estimate, only employer exclusions will be allowed for detailed targeting.
  As a result of this change, custom audiences will be deprecated within the exclusions field. You can still continue using custom audience exclusions by using the excluded_custom_audiences field instead. For more details see Advanced Targeting: Custom Audiences.
  The following endpoints are affected:
• POST /{ad-account-id}/adsets
• POST /{adset-id}
• POST /{adset-id}/copies
• GET /{ad-account-id}/delivery_estimate

Reach People Interested in Selected Cities and Regions

Applies to v22.0+.
Expands location targeting beyond an ad campaign's target cities or regions to deliver ads to people who have shown interest in a location.
The following endpoints are affected:

• POST /{ad-account-id}/adsets
• POST /{adset-id}
• GET /{adset-id}
• GET /{ad-account-id}/delivery_estimate

Commerce Platform

Promotions API – field deprecation

Applies to v22.0+.
The promotions field has been deprecated and replaced by the promotion_details field. Please discontinue using the promotions field, as it does not contain complete information. Please migrate your API calls to the new promotion_details field.
The following endpoint is affected:

• GET /{commerce-order-id}/promotion_details

Instagram Endpoints

Applies to v22.0+. Will apply to all versions April 21, 2025.
The Instagram endpoints supported by the Marketing API have been deprecated.
The following endpoints are affected:

• DELETE /{instagram-comment-id}
• GET /{instagram-carousel-id}
• GET /{instagram-carousel-id}/comments
• GET /{instagram-comment-id}
• GET /{instagram-comment-id}/replies
• GET /{instagram-media-id}
• GET /{instagram-media-id}/comments
• GET /{instagram-user-id}
• GET /{instagram-user-id}/agencies
• GET /{instagram-user-id}/ar_effects
• GET /{instagram-user-id}/authorized_adaccounts
• GET /{instagram-user-id}/upcoming_events
• POST /{instagram-user-id}/authorized_adaccounts
• POST /{instagram-carousel-id}/comments
• POST /{instagram-comment-id}
• POST /{instagram-comment-id}/replies
• POST /{instagram-media-id}
• POST /{instagram-user-id}/upcoming_events
  Please migrate your API calls to use the following Instagram Platform endpoints:
• IG User
• IG Media
• IG Media Children
• IG Comment
• IG Comment Replies

Special Ad Categories

We are providing an update regarding the previously considered restrictions on customer list custom audiences (CLCAs) for advertisers offering housing, employment, and financial products and services in or targeting audiences in the United States.
The rollout of these previously announced restrictions will not proceed.
Certain customer list custom audiences will become ineligible for usage in ad sets of housing, employment, and financial products and services, including credit, campaigns beginning March 2025. Learn more about the update here and whether the restrictions apply to you.

Ad Sets for Special Ad Category Campaigns

Applies to v22.0+. Will apply to all versions March 2025.
Starting with v22.0, you will be unable to create or update ad sets if their targeting options contain one or more ineligible customer list custom audiences. You will need to either certify if eligible or remove any such audiences to successfully create or update the ad set. Starting early April 2025, existing campaigns/ad sets using customer list custom audiences which do not follow the requirements may be paused. If this happens, you will see errors in Ads Manager and the Marketing API with instructions.
The is_sac_cfca_terms_certified field will be added to the ad set API. You will be required to use this field to certify that any customer list custom audiences being used in an ad set of a housing, employment, and financial products and services, including credit, campaign comply with Meta’s CLCA certification.
This change affects the following endpoints when creating or updating ad sets:

• POST /{ad-account-id}/adsets
• POST /{ad-set-id}

Custom Audiences

Applies to all versions.
Starting on January 6, 2025, you can use the new is_eligible_for_sac_campaigns field to identify whether a custom audience can be used in ad sets of Special Ad Category campaigns. You must provide the intended special_ad_categories and special_ad_category_countries of the Special Ad Category campaign using the audience, as well as the ad_account_id which will use the audience to create or edit the ad set.
This change affects the following endpoints:

• GET /{custom-audience-id}
  See Special Ad Categories for more information about these changes.

Original source

Graph API

Released October 2, 2024 | Available until TBD | Blog post

Instagram Platform

Media Insights

Applies to v21.0+. Will apply to all versions on January 8, 2025.
The video media metric video_views will no longer be supported.
The following endpoints and metrics are affected:

• GET /{ig-media-id}/insights
  • video_views

User Insights

Applies to v21.0+. Will apply to all versions on January 8, 2025.
The email_contacts, get_direction_clicks, profile_views, text_message_clicks, website_clicks, and phone_call_clicks time series metrics will no longer be supported.
The following endpoints and metrics are affected:

• GET /{ig-user-id}/insights
  • email_contacts
  • get_direction_clicks
  • profile_views
  • text_message_clicks
  • website_clicks
  • phone_call_clicks

Messaging Events API

• Messaging Events API will be deprecated in September 2025. To prepare for this deprecation, Messaging Events API will no longer be supported in any future releases of Graph API, starting with version 21.0, as of September 24, 2024.
• Partners who choose not to update to the latest Graph API will still be able to access Messaging Events API by calling Graph API version 20.0 or prior until the official product deprecation in September 2025.
• For Partners who do not update to the latest Graph API, we recommend they use the Conversions API for new integrations. Learn more about the Conversions API.
  The following endpoints are affected:
• POST /{app_id}/page_activities

WhatsApp

See the WhatsApp Business Platform changelog.

Marketing API

Released October 2, 2024 | Available until TBD | Blog post

Objectives

Outcome-Driven Ad Experiences
Applies to v21.0+.
Beginning with v21.0, you will no longer be able to create new ad sets or ads with non-Outcome-Driven Ad Experience (ODAX) objectives. Existing ad campaigns using older objectives can continue to run for now, but we encourage you to transition all your campaigns to the ODAX objectives. See the Simplifying campaign objectives with Outcome-Driven Ad Experiences blog entry and the Outcome-Driven Ad Experiences documentation for more information.
The following endpoints are affected:

• POST /{ad_account_id}/campaigns
• POST /{ad_account_id}/ads
• POST /{ad_account_id}/adsets
• POST /{campaign_id}
• POST /{ad_group_id}

Standard Enhancements

Image Expansion
Applies to v21.0+.
For single media ads, the Image Expansion feature will be included as part of Standard Enhancements. Therefore, if creating an ad or an ad creative opted-in to Image Expansion, please refer to this link for instructions to set standard_enhancements as a field inside the creative_features_spec.
The following endpoints are affected:

• POST /{ad_account_id}/adcreatives
• POST /{ad_account_id}/ads
• GET /{ad_id}/previews
• GET /{ad_account_id}/generatepreviews

Version 22 Upcoming Change

Product Catalog — Enforcing Country Override Specific Fields
Applies to v22.0
This change applies to advertisers using country and language feeds to localize their product data. It standardizes which fields should be provided in a country feed versus a language feed (or a country and language feed via API) to help advertisers set up their product data in the most efficient way.
Price, sale price, unit price, base price, status (visibility), and availability must now only be provided in a country feed. This helps ensure customers see the correct localized product data.
If your language feed currently contains the price, sale_price, base_price, status, or availability fields, move them to your country feed before the Graph API v22.0 release in Q1 2025 to ensure that the localized data continues to be uploaded to your products past this date.
The following endpoints are affected:

• POST /{product-catalog-id}/localized_items_batch

Original source

Graph API

Released May 21, 2024 | Available until TBD | Blog Post

Comments

Applies to v20.0. Applies to all versions August 19, 2024.

Changed the permalink_url field on the Comment node. This field will not be returned in API responses for comments on posts on pages if the calling app has only the Page Public Content Access feature.

Error Codes

Applies to v20.0+.
The API will now return error code 200 instead of error code 2 when the calling app's user does not have permission to access a given field on a given object.

Instagram Graph API

Instagram User Insights

Applies to v20.0+. Will apply to all versions on August 19, 2024.
The last_14_days, last_30_days, last_90_days, and prev_month timeframes will no longer be supported for the reached_audience_demographics and engaged_audience_demographics metrics.
The following endpoints and metrics are affected:

• GET /{ig-user-id}/insights
  • engaged_audience_demographics
  • reached_audience_demographics

Messenger Platform

The Booking button is no longer supported in Messenger API calls. This change does not affect other templates and buttons, and businesses can still manage bookings using Meta Business Suite. We recommend reviewing your current integrations and adjusting your applications as necessary to ensure a smooth transition for your users.

WhatsApp Flows

See WhatsApp Flows changelog.

Marketing API

Released May 21, 2024 | Available until May 6, 2025 | Blog Post

Auction Ads

Campaign Optimization of Impressions

Applies to v20.0+. Will apply to all versions August 19, 2024.
The optimization_goal parameter will no longer accept the impressions value in combination with:

• The legacy POST_ENGAGEMENT objective
• The ON_POST destination_type
  Note: Optimizing for reach is still available.
  The following endpoints are affected:
• POST /{ad-account-id}/adsets

Frequency Controls

Applies to v20.0+. Will apply to all versions August 19, 2024.
The frequency_control_specs parameter should no longer be sent in an API call if the optimization_goal is set to Ad Recall Lift, Link Click Optimization, Post Engagement, or 2-second Video Views. Any campaigns of this type that are still running will be disabled beginning August 19, 2024.
Writes to this field are only available in ad sets where REACH and THRUPLAY are the performance goal.
The following endpoints are affected:

• POST /{ad-account-id}/adsets

Offline Conversions API

Deprecation of Remaining Endpoints

Applies to v20.0+.
The Offline Conversions API will be discontinued in May 2025. It was previously due to be deprecated in the third quarter of 2024. As we announced in the v17.0 changelog, the Offline Conversions API no longer supports offline events. Graph API v16.0 is the last version that supports offline events. The Offline Conversions API will be discontinued when v16.0 expires in May 2025.
Between now and May 2025, we will be deprecating the remaining Offline Conversions API endpoints on Marketing API v20.0.
The following endpoints are affected:

• POST/GET/DELETE /{offline_event_set_id}
• POST/GET /{offline_event_set_id}/uploads
• POST /{offline_event_set_id}/validate
• POST /{offline_event_set_id}/ad_account
• GET /{offline_event_set_id}/stats
• GET /{offline_event_set_id}/shared_agencies
• POST/GET /{offline_event_set_id}/agencies
• GET /{offline_event_set_id}/adaccounts
• GET /{offline_event_set_id}/customconversions
• GET /{offline_event_set_id}/audiences
• GET /{offline_event_set_id}/shared_accounts
• GET /{ad_account_id}/offline_conversion_data_sets
• POST/GET /{business_id}/offline_conversion_data_sets
• POST/GET/DELETE /{business_asset_group_id}/contained_offline_conversion_data_sets
  In February 2023, we announced that the Conversions API now fully supports offline events. We recommend that advertisers use the Conversions API for new integrations. We recommend that advertisers with Offline Conversions API integrations convert their integration into a Conversions API integration before May 2025 and not update their Offline Conversions API until they have successfully done so. Learn more about the Conversions API.

Messaging Ads

Sponsored Messages

Applies to v20.0+. Will apply to all versions August 19, 2024.
Creation of the sponsored messages ad type will no longer be available. This change will not affect other messaging ads ad types.
The following endpoints are affected:

• POST /{ad-account-id}/adcreatives

Original source

Graph API

Released January 23, 2024 | Available until May 21, 2026 | Blog Post

Groups API

Applies to v19.0. Will apply to all versions April 22, 2024.
Deprecated the following Groups API permissions and features:

• publish_to_groups
• groups_access_member_info
• Groups API
  You can verify if a given Groups API endpoint requires one of these permissions or features by making a version 19 request on the endpoint (https://graph.facebook.com/v19.0/...).
  In addition, we have deprecated the ability for group admins to install apps on the group, even if they have an admin or developer role on the app.
  These permissions, features, and abilities will be removed April 22, 2024.

WhatsApp Flows

See WhatsApp Flows changelog.

Marketing API

Released January 23, 2024 | Available until February 4, 2025 | Blog Post

Insights Ads Insights

Applies to v19.0+.

• The age_targeting, gender_targeting, labels, and location insights metrics will no longer be available.
• The estimated_ad_recall_rate_lower_bound, estimated_ad_recall_rate_upper_bound, estimated_ad_recallers_lower_bound, and estimated_ad_recallers_upper_bound insights metrics will no longer be available.
  The following endpoints are affected:
• GET /{ad-set-id}/insights
• GET /{ad-account-id}/insights
• GET /{ad-id}/insights
• GET /{campaign-id}/insights
• POST /{ad-set-id}/insights
• POST /{ad-account-id}/insights
• POST /{ad-id}/insights
• POST /{campaign-id}/insights

Objectives Ad Copies

Applies to v19.0+.
When creating a copy of an ad you must only use Outcome-Driven Ad Experience objectives. Attempting to use legacy objectives will result in an error.
The following endpoints are affected:

• POST /{adgroup-id}/copies
• POST /{ad-campaign-id}/copies
• POST /{ad-campaign-group-id}/copies

Targeting

####### Target Expansion

Applies to v19.0+. Will apply to all versions on April 22, 2024.

• The targeting_optimization field will not be accepted for campaigns that are optimized for link clicks or landing page views. This also applies to previous optimizations that were included in Advantage Detailed Targeting with no option to opt-out including conversions, value, app installs, app events and conversations.
• For all optimizations that are opted into Advantage Detailed Targeting with no option to opt-out we will automatically set the targeting_as_signal field to either 1 or 3 based on the set of objectives and optimizations.
• The targeting_as_signal field should be either null or 0 for campaigns that are optimized for impressions, video views, reach, engagement, ad recall lift or lead, otherwise an error will be received.
  The following endpoints are affected:
• POST /act_{ad-account-id}/adsets
• POST /{adset-id}
• GET /{adset-id}/delivery_estimate
• GET /act_{ad-account-id}/delivery_estimate

Original source

Graph API

Released September 12, 2023 | Available until January 26, 2026 | Blog Post

Instagram Graph API

Deprecation of Media and User Insights

Applies to v18.0+. Will apply to all versions on December 11, 2023.
Duplicative and legacy Instagram insight metrics are being deprecated. Please see documentation for the endpoints and Instagram Insights for more information on which metrics to use in their place.
The following endpoints and metrics are affected:

• GET /{ig-user-id}/insights
  • AUDIENCE_GENDER_AGE
  • AUDIENCE_LOCALE
  • AUDIENCE_COUNTRY
  • AUDIENCE_CITY
• GET /{ig-media-id}/insights
  • CAROUSEL_ALBUM_IMPRESSIONS
  • CAROUSEL_ALBUM_REACH
  • CAROUSEL_ALBUM_ENGAGEMENT
  • CAROUSEL_ALBUM_SAVED
  • CAROUSEL_ALBUM_VIDEO_VIEWS
  • TAPS_FORWARD
  • TAPS_BACK
  • EXITS
  • ENGAGEMENT
    Note: total_interactions, which is listed as an alternative for some of the deprecated metrics, is currently only available using version 18.0 and does not work with older versions. When querying older versions before Dec 11, 2023, please use the engagement metric.

Server-Sent Events

Server-Sent Events are deprecated and will be removed December 31, 2023.

WhatsApp

See the WhatsApp Business Platform changelog.

Marketing API

Released September 12, 2023 | Available until August 13, 2024 | Blog Post

Catalog API

Credit Cards

Applies to v18.0+.
The {ad-account-id}/credit_cards endpoint is no longer supported.

Reach and Frequency

Reach and Frequency Campaigns

Applies to v18.0+.

Objective

• Target frequency can now be used for REACH and VIDEO_VIEWS objectives in reach and frequency campaigns.
• The objective parameter will no longer accept TRAFFIC unless the rf_prediction_id_to_share parameter is set to a valid prediction ID.

Optimizations

• Reach and frequency campaigns can now use the REACH optimization.
• The optimization_goal parameter will no longer accept POST_ENGAGEMENT or LINK_CLICKS unless the rf_prediction_id_to_share parameter is set to a valid prediction ID.
• The frequency_cap parameter will no longer accept any value greater than 0 if the optimization_goal parameter is set to AD_RECALL_LIFT. AD_RECALL_LIFT predictions will be generated without applying any frequency cap.

The following endpoints are affected:

• POST /act_{ad-account-id}/reachfrequencypredictions

Targeting Location Targeting

Applies to v18.0+. Will apply to all versions December 11, 2023.
When no location_types is sent in the API call, it will default to ['home', 'recent'].
The following endpoints are affected:

• GET /act_{ad-account-id}/reachestimate
• GET /act_{ad-account-id}/delivery_estimate
• POST /act_{ad-account-id}/adsets
• POST /{adset-id}

Location Targeting Deprecation

Applies to v18.0+.
All options other than ['home','recent'] will be deprecated for location_types. Trying to use any options other than ['home', 'recent'] will result in an error.
The following endpoints are affected:

• GET /act_{ad-account-id}/reachestimate
• GET /act_{ad-account-id}/delivery_estimate
• POST /act_{ad-account-id}/saved_audiences
• POST /act_{ad-account-id}/adsets
• POST /{adset-id}
• POST /{saved-audience-id}

Original source

This changelog was updated with the following changes:

• September 19, 2023: Added User Accounts entry
• December 19, 2023: Moved Offline Conversions API information from Marketing API to Graph API
• February 6, 2024: Added affected endpoints for Ad Strategies

Graph API

Released May 23, 2023 | Available until September 12, 2025 | Blog Post

Instant Articles

As of April 20, 2023, the Instant Articles API no longer returns data. All Instant Articles API endpoints are not available on v17 or later and will be removed for all versions on August 21, 2023.

Offline Conversions API

Deprecation of Offline Conversions API

Applies to v17.0+.
Starting with Graph API v17.0, the Offline Conversions API will no longer support offline events. Graph API v16.0 is the last version that supports offline events. We anticipate that the Offline Conversions API will be discontinued in the third quarter of 2024.
In February 2023, we announced that the Conversions API now fully supports offline events. We recommend that advertisers use the Conversions API for new integrations. We recommend that advertisers with Offline Conversions API integrations convert their integration into a Conversions API integration before the third quarter of 2024 and not update their Offline Conversions API until they have successfully done so. Learn more about the Conversions API.
The following endpoint is affected:

• POST /{offline_event_set_id}/events

ThreatExchange

The /malware_analyses endpoint is deprecated. It is not available on v17 or later and will be removed for all versions on August 21, 2023.

User Accounts

This entry was added on September 19, 2023.
Applies to v17.0 and later versions. Will apply to all versions on September 15, 2023 (UPDATE: No longer applies to all versions. See September 15, 2023 out-of-cycle change.)
The GET /{user-id}/accounts (aka GET /me/accounts) endpoint no longer returns Facebook pages that have been linked to a Meta business account, unless the app user has granted the business_management permission to the app and has a role on the linked business account.

WhatsApp

See the WhatsApp Business Platform changelog.

Marketing API

Released May 23, 2023 | Available until May 14, 2024 | Blog Post
Marketing API version auto-upgrade will release on May 14, 2024.

Original source

Graph API

Released February 2, 2023 | Available until May 14, 2025 | Blog post
Comment, Photo, Post, Video
Applies to v16.0+. Will apply to all versions May 3, 2023.

The following fields on comments, photos, posts, and videos created on a user profile will now return an empty data set:

• comments
• message_tags
• reactions
• sharedposts
• story
• story_tags
• to
• via

Encryption

Applies to v16.0+. Will apply to all version May 3, 2023.
TLS versions older than 1.2 and static RSA cipher suites are no longer supported. See Encryption.

Messenger Platform

See the Messenger Platform changelog.

WhatsApp Business Platform

See the WhatsApp Business Platform changelog.

Marketing API

Released February 2, 2023 | Available until February 6, 2024 | Blog post

Ads Placement

Instant Articles

Applies to v16.0+. Will apply to all versions on April 20, 2023.
Advertisers will no longer be able to target the Instant Article placement for ads creation.
The following endpoints will be affected:

• GET /{ad-account-id}/adsets
• POST /{ad-account-id}/adsets
• GET /{ad-set-id}?fields=targeting

Travel Ads

Flight Ad Prospecting

Applies to v16.0+.
Prospecting is no longer an available audience option when creating a flight ad. New campaigns will only including retargeting audiences and require a data source.
The following endpoints and fields are affected:

• POST /{ad-account-id}/adsets

Trip Consideration

Applies to v16.0+.
The Reach Potential Travelers option is no longer available. System improvements will automatically prioritize delivery to Account Center accounts that may be planning travel. Campaigns are expected to achieve similar performance.
The following endpoints are affected:

• POST /{ad-account-id}/adsets

Original source

Graph API

Released September 15, 2022 | Available until November 20, 2024 | Blog post

Instagram Graph API

Story Webhooks

Applies to all versions.
Story insights webhooks notifications are now sent 1 hour after story expiration.

Pages API

Custom Page Tabs

Applies to v15.0+. Will apply to all versions December 14, 2022.
Custom Page Tabs are no longer available. The following endpoints are affected:

• POST /{page-id}/tabs
• DELETE /{page-id}/tabs

Marketing API

The expiration date for Marketing API v14.0 and v15.0 has been moved to September 20, 2023 from August 15, 2023 to provide more time for the platform integrating changes for DSA enforcement. Note v14.0 and v15.0 will expire on the same day. To avoid disruption to your apps, we recommend upgrading to our latest version before September 20.
Released September 15, 2022 | Available until September 20, 2023 | Blog post

Audiences

Special Ad Audiences

Applies to all versions.
Special Ad Audiences, which are similar to lookalike audiences for housing, employment, and credit advertisers, have been deprecated due to a settlement with the US Department of Housing and Urban Development. See the developer blog for more information about this announcement.
You can no longer create Special Ad Audiences. Special Ad Audiences endpoints will be removed no later than December 31, 2022.
The following endpoints and fields are affected:

• GET /{ad-account-id}/customaudiences?fields=operation_status
• POST /{ad-account-id}/adsets?fields=subtype
• POST /{ad-account-id}/customaudiences?fields=subtype
• POST /{ad-campaign-id}?fields=subtype
• POST /{custom-audience-id}

Advantage Custom Audiences

Applies to v15.0+. Will apply to all versions on December 14, 2022.
When creating an ad set with any objective and with a non-data file custom audience in inclusion, Advantage custom audiences will be turned on by default.
When creating an ad set with a non-Advantage lookalike objective (that is, Value Optimization, Offsite Conversion, App Installs and Messages) with lookalike in inclusion, Advantage lookalike will be turned on by default.
Advantage custom audience and Advantage lookalike can be enabled or disabled through the targeting_relaxation_types targeting spec parameter. targeting_relaxation_types accepts either custom_audience and lookalike as a key, and if a value of 0 is passed, it will be disabled. If a value of 1 is passed, it will be enabled. If no key/value pair is passed, it will be considered as enabled.
The following endpoints and fields are affected:

• GET /{ad-account-id}/adsets
• POST /{ad-account-id}/adsets
• GET /{ad-set-id}?fields=targeting

Advantage Detailed Targeting

Applies to v15.0+. Will apply to all versions on December 14, 2022.
When creating an ad set with the Messages or App Installs optimization goals, Advantage lookalike and/or Advantage detailed targeting will be turned on by default and cannot be disabled.
When querying ad sets with the Messages or App Installs optimization goals that have Advantage detailed targeting and/or Advantage lookalike enabled, a targeting_optimization_types map will be returned with the detailed_targeting and lookalike properties indicating that the expansion is enabled. When querying delivery estimates for ad sets with the Messages or App Installs optimization goals, the targeting_optimization field will no longer be accepted and an error will be thrown.
For existing ad sets, you will be able to pass the targeting_optimization field.
The following endpoints are affected:

• GET /{ad-account-id}/adsets
• POST /{ad-account-id}/adsets
• GET /{ad-set-id}/delivery_estimate

Campaigns

Deprecated optimization type
Applies to v15.0+. Will apply to all versions on December 14, 2022.
Beginning September 15, 2022, advertisers will no longer be allowed to create incremental conversion optimization campaigns. Existing conversion optimization campaigns will behave normally.
The following endpoint is affected:

• POST /{ad_account_id}/campaigns

Custom Conversions

Applies to v15.0+.
We now require new Custom Conversions to contain at least one rule when they are created. Otherwise, campaigns should optimize on the event directly.
The following endpoint is affected:

• POST /{ad_account_id}/customconversions

Original source

Graph API

Released May 25, 2022 | Available until September 17, 2024 | Blog post

Instagram Graph API

Insights

Applies to v14.0+.
The end_time JSON property will not be returned for any audience_* metrics.

Instagram Messaging API

User Profile

Applies to v14.0+
You can now use the User Profile API to get an app user's username.

Payments Risk action type

Applies to v14.0+.
The risk action type of the actions field (GET /{payment-id}?fields=actions) has been removed and will not be returned.

Permissions

user_likes

Applies to all versions.
The user_likes permission's allowed usage has changed. The new allowed usage is:

• Provide a personalized experience by correlating or surfacing content related to the person’s likes. This includes curating content at scale to customize apps with large amounts of content and to enable people to share their likes with others, such as in the case of dating and music apps.
• Allow parental access controls and monitoring apps to analyze user likes for potential safety and wellbeing issues for people under 18 years old, as used solely by parents and guardians for under 18 year old dependents and limited to youth social media analysis as presented in the app’s user interface.

user_posts

Applies to all versions.
The user_posts permission's allowed usage has changed. The new allowed usage is:

• Enable people to create physical or digital books or albums of their timelines, and to share memories from their timeline on Facebook or on other social apps.
• Allow parental access controls and monitoring apps to analyze a post's content to detect potential risk to safety or wellbeing for people under 18 years old, as used solely by parents and guardians for under 18 year old dependents and limited to youth social media analysis as presented in the app’s user interface.

WhatsApp

See the Whatsapp changelog.

Marketing API

The expiration date for Marketing API v14.0 and v15.0 has been moved to September 20, 2023 from August 15, 2023 to provide more time for the platform integrating changes for DSA enforcement. Note v14.0 and v15.0 will expire on the same day. To avoid disruption to your apps, we recommend upgrading to our latest version before September 20.
Released May 25, 2022 | Available until September 20, 2023 | Blog post
No changes.

Original source

Graph API

Released February 8, 2022 | Available until TBD | Blog post

Instagram Graph API

IG Media

Version 13 will be the last version to allow video_title field requests on IG Media without returning an error. As a reminder, the current API behavior outlined in our October 5th, 2021 blog post is as follows:

• media_product_type field returns FEED for all versions
• video_title field is omitted from responses for all versions
• Instagram Webhooks comments and mentions fields are supported for all versions

The behavior above applies to all IG Media, including IG Media created with the Instagram TV app, regardless of creation date.

User Insights

Applies to v13.0+
The following IG User Insights metrics no longer support since and until parameters, and responses will not include the end_time JSON property.

• audience_city
• audience_country
• audience_gender_age
• audience_locale

Marketing API

Released February 8, 2022 | Available until January 25, 2023 | Blog post

Ad Creative Placement Asset Customization Ads

Applies to v13.0+.
The asset_feed_spec node of the POST /{ad-account-id}/adcreatives endpoint will now allow the creation of carousel ads with Placement Asset Customization ads.

Ads Library API Ads Archive

Applies to v13.0+.
The following query edges and fields on the GET /ads_archive endpoint have been deprecated and replaced:
Old Edge/Field -> New Edge/Field

• funding_entity -> bylines
• region_distribution -> delivery_by_region
• potential_reach_min -> estimated_audience_size_min
• potential_reach_max -> estimated_audience_size_max
• potential_reach -> estimated_audience_size

The following return parameters on the GET /ads_archive endpoint have been deprecated and replaced:

• ad_creative_body -> ad_creative_bodies
• ad_creative_link_caption -> ad_creative_link_captions
• ad_creative_link_description -> ad_creative_link_descriptions
• ad_creative_link_title -> ad_creative_link_titles
• funding_entity -> bylines
• region_distribution -> delivery_by_region

Ad Sets Lookalike Expansion

Applies to v13.0+. Will apply to all versions May 9, 2022.
For newly created ad sets that optimize for value, conversions, or app events, lookalike expansion will be turned on by default and cannot be disabled. When getting an ad set that optimizes for value, conversions, or app events, we will return a new lookalike property in the targeting_optimization_types map that indicates lookalike expansion is enabled and complements the existing detailed_targeting property for the detailed targeting expansion.
This change affects the following endpoints:

• POST /{ad-account-id}/adsets
• GET /{ad-account-id}/adsets

Conversions API Customer Information Parameters

Applies to v13.0+.
There are new requirements for the combinations of customer information parameters that are considered valid for an event. An event will be considered invalid if it only includes parameters consisting of one of the following combinations or a subset thereof:

• ct + country + st + zp + ge + client_user_agent
• db + client_user_agent
• fn + ge
• ln + ge
  To ensure your events do not throw an error, we recommend that you review the Conversions API Best Practices.
  This change affects the following endpoints:
• POST /{pixel-id}/events
• POST /{offline_dataset_id}/events

Commerce Platform Shipping Profiles API

Applies to v13.0+.
The handling_time field of the GET /{cms-id}/shipping_profiles endpoint has been moved from the shipping_profile object to the address_category object.

Catalog Feed API

Applies to v13.0+.
The product feed upload error code XML_JUNK_AFTER_DOCUMENT has been renamed to DATA_OUTSIDE_XML_TAGS. This is a name change only.
The following endpoint is affected:

• GET /{feed_upload_session_id}

Original source

Graph API

Released September 14, 2021 | Available until TBD | Blog post

App Insights

Endpoint Deprecation

Applies to v12.0+.
The App Insights API is deprecated. Affected endpoints:

• GET /{application-id}/app_insights

Errors

Endpoints that now throw errors
Applies to v12.0+. Will apply to all versions December 13, 2021.
The Graph API default behavior is to throw an error when an app requests a field or edge that returns an associated node or nodes, but lacks the appropriate permissions required by the associated nodes. Fields and edges on the endpoints listed below did not follow this protocol and instead were omitted from API responses when the calling app lacked appropriate permissions. Starting with version 12.0, these fields and edges will now conform to the default behavior. This change will apply to all versions on December 13, 2021.

• GET /{application-id}/authorized_adaccounts
• GET /{atlas-fb-conversion-event-id}/fb_ads_conversion
• GET /{business-unit-id}/ad_accounts
• GET /{business-unit-id}/atlas_sales_accesses
• GET /{canvas-product-set-id}/storefront_setting
• GET /{commerce-merchant-settings-id}/instagram_channel
• GET /{commerce-store-id}/merchant_settings
• GET /{destination-id}/augmented_realities_metadata
• GET /{destination-id}/videos_metadata
• GET /{event-id}/ticket_tiers
• GET /{flight-id}/augmented_realities_metadata
• GET /{flight-id}/videos_metadata
• GET /{live-encoder-id}/current_broadcast
• GET /{live-video-id}/copyright
• GET /{page-id}/admin_notes
• GET /{page-id}/businessprojects
• GET /{page-id}/connected_instagram_account
• GET /{page-id}/connected_page_backed_instagram_account
• GET /{page-id}/insights_exports
• GET /{page-id}/instagram_business_account
• GET /{ig-comment-id}/user
• GET /{ig-media-id}/owner
• GET /{ig-user-id}/mentioned_comment
• GET /{user-id}/adaccounts
• GET /{user-id}/assigned_ad_accounts
• GET /{user-id}/context
• GET /{user-id}/personal_ad_accounts
• GET /{video-copyright-id}/update_records

Instagram Messaging API

New User Profile Fields

Applies to v12.0+
Added four new fields to the GET /{ig-scoped-id} endpoint:

• is_verified_user
• follower_count
• is_user_follow_business
• is_business_follow_user

Live Video API

Scheduled Live Videos

Will apply to all versions December 13, 2021.
UPDATE: This deprecation has been delayed.
Scheduling live videos is no longer available. The planned_start_time parameter for the POST /ID/live_videos endpoint is deprecated. Calls using this parameter will return an error._
Affected endpoints:

• POST /{group-id}/live_videos
• POST /{page-id}/live_videos
• POST /{user-id}/live_videos

Messenger Platform

Multiple changes have been introduced that affect several Messenger APIs and webhooks. Please refer to the Messenger Platform changelog for a summary of these changes.

Video API

New Fields

Applies to v12.0+.
Added two new fields to the GET /{video-id} endpoint:

• post_views
• views

Workplace

Reported Content

Applies to v12.0+.
The reported_object_id field for the GET /company/reported_content endpoint is deprecated. Calls to this field will return no data. Use the new GET /reported_content/reporters endpoint instead.
Added six new endpoints:

• /REPORTED-CONTENT-ID
• GET /reported_content/reporters
• POST /REPORTED-CONTENT-ID/allow_content
• POST /REPORTED-CONTENT-ID/delete_content
• POST /REPORTED-CONTENT-ID/quarantine_content
• POST /REPORTED-CONTENT-ID/unquarantine_content

Marketing API

Released September 14, 2021 | Available until August 9, 2022 | Blog post

Ad Sets Targeting

Applies to v12.0+. Will apply to all versions December 13, 2021.
When optimizing for Value, Conversions, or App Events, detailed targeting inclusions will not affect the potential reach and may go beyond detailed targeting inclusions to improve performance. The new targeting_optimization_types parameter will indicate which targeting options are used as a signal for optimization.
The following endpoints will be effected:

• GET /{adset-id}
• GET /{adset-id}/delivery_estimate
  The POST /{adset-id} endpoint will return an error for updates to newly created ad sets with Value, Conversions or App Events as the optimization goals within Conversions objective campaigns using the targeting_optimization field. Existing ad sets will continue allowing changes to the field.
  The POST /{ad-account-id}/adsets endpoint will return an error if the targeting_optimization field is passed when creating a new ad set using Value, Conversions, or App Events as the optimization goals within Conversions objective campaigns. The targeting_as_signal field will be ignored when passed during ad set creation.

Business Management API

System User App Role Requirements

Applies to v12.0+. Will apply to all version December 13, 2021.
A system user can now only be granted a role on app if both the system user and the app belong to the same business. On December 13, 2021, app roles will be revoked for any system user who has a role on an app that does not belong to the same business as the system user.
If your app needs to access data using a system user and access token belonging to another business, use the Business On Behalf Of API instead.

Errors

Endpoints that now throw errors
Applies to v12.0+. Will apply to all versions December 13, 2021.
The Marketing API default behavior is to throw an error when an app requests a field or edge that returns an associated node or nodes, but lacks the appropriate permissions required by the associated nodes. Fields and edges on the endpoints listed below did not follow this protocol and instead were omitted from API responses when the calling app lacked appropriate permissions. Starting with version 12.0, these fields and edges will now conform to the default behavior. This change will apply to all versions on December 13, 2021.

• GET /{ad-account-id}/ad_saved_keywords
• GET /{ads-pixel-id}/shared_accounts
• GET /{ad-study-cell-id}/adaccounts
• GET /{business-id}/client_ad_accounts
• GET /{business-id}/collaborative_ads_managed_partner_business_info
• GET /{business-id}/extendedcreditapplications
• GET /{business-id}/owned_ad_accounts
• GET /{business-user-id}/assigned_ad_accounts
• GET /{custom-audience-id}/external_event_source
• GET /{custom-conversion-id}/pixel
• GET /{extended-credit-invoice-group-id}/ad_accounts
• GET /{hotel-id}/augmented_realities_metadata
• GET /{hotel-id}/videos_metadata
• GET /{instagram-user-id}/authorized_adaccounts
• GET /{lead-gen-data-id}/context_card
• GET /{lead-gen-data-id}/thank_you_page
• GET /{offline-conversion-data-set-id}/adaccounts
• GET /{offline-conversion-data-set-upload-id}/pull_sessions
• GET /{product-catalog-id}/auto_markets
• GET /{product-catalog-id}/autos
• GET /{product-catalog-id}/commerce_merchant_settings
• GET /Produ{product-catalog-id}ctCatalog/media_titles
• GET /{product-catalog-id}/services
• GET /{product-feed-id}/auto_markets
• GET /{product-feed-id}/autos
• GET /{product-feed-id}/media_titles
• GET /{product-set-id}/media_titles
• GET /{system-user-id}/assigned_ad_accounts
• GET /{vehicle-id}/augmented_realities_metadata
• GET /{vehicle-id}/videos_metadata

Conversions API

Change to access tokens

Applies to v12.0+
Access tokens generated under the Conversions API settings tab in Events Manager are no longer restricted to using the newest Graph API version that was available at the time of token generation. Starting with v12.0, newly created access tokens can be used with all available Graph API versions.
Please note that calls made with these tokens to a deprecated Graph API version will automatically resolve to the oldest available version. This behavior only applies to Graph API endpoints. Marketing API endpoints, including the Conversions API, will not resolve to the oldest available version and will instead throw an exception.

Catalog API

Deprecation of review_status field

Applies to v12.0+
The review_status field on the Product Item node is deprecated. This field has been unreliable and is no longer used in our internal system. Starting with version 12.0, review_status will not be accepted as a valid field. We recommend that you use the channels_to_integrity_status field instead. Please note that for version 11.0 and earlier, the review_status field will always return an empty string.
This change affects the following endpoints:

• GET /{catalog_id}/products?filter={"review_status":{"eq":{enum}}}
• GET /{catalog_id}/products?fields=["name","review_status"]

Catalog permissions

Applies to v12.0+. Will apply to all versions December 13, 2021.
If a user does not have business administrator permissions on the business associated with a catalog, they will not be able to modify catalog permissions.
The following edges are affected:

• POST /{product-catalog-id}/assigned_users
• DELETE /{product-catalog-id}/assigned_users
• POST /{product-catalog-id}/agencies
• DELETE /{product-catalog-id}/agencies

Original source

Graph API

Released June 8, 2021 | Available until September 14, 2023 | Blog post

Consumer Apps

Access Levels

Applies to all versions.
In the coming weeks, access levels will apply to all existing Consumer apps. For these apps, permissions and features already approved through the App Review process will be automatically approved for Advanced Access. All other permissions and features will automatically be approved for Standard Access.
Access levels will also apply to all newly created apps in the coming weeks. Newly created apps will automatically be approved for Advanced Access for the email and public_profile permissions. However, both permissions will be set to Standard Access by default and must manually be set to Advanced Access before they can be requested from app users who do not have roles on the apps.

Developer Support

We have released the Facebook for Business Status tool to monitor the health of platform and business products such as Ads Manager, WhatsApp Business, and Facebook Developer Platform.

Facebook Analytics

Deprecation

Applies to all versions.
Facebook Analytics will no longer be available after June 30, 2021. Additionally, we are deprecating the App Dashboard Plugin for Marketing API. For more information visit the Business Help Center.
The following Application Node fields are no longer available:

• analytics_config
• analytics_platform_metrics_config
• permissible_ad_accounts
  The following endpoints are no longer available:
• GET Application/analytics_cohort_query
• GET Application/analytics_entity_user_config
• GET Application/analytics_event_types
• GET Application/analytics_funnel_query
• GET Application/analytics_query
• GET Application/analytics_segments

Instagram Basic Display API

Access Token Debugger

Applies to all versions.
The access token debugger tool now only returns an app-scoped ID when debugging a token.

API Versioning

Applies to all versions.
The API now supports versioned calls. To query a specific API version include the version number in the query path after the base URL. For example:
https://graph.instagram.com/v11.0/{node-id}/{edge-name}
Un-versioned requests (missing the version number) resolve to the version specified in the calling app's App Dashboard > Settings > Advanced > Upgrade API Version setting.

App Scoped User IDs

Applies to version 11.0+.
App-scoped user IDs (ASIDs) have been introduced. ASIDs will replace raw user IDs in approximately two years, when version 10.0 is deprecated, so we recommend that you begin mapping your app users' raw IDs to their ASID equivalents.

• All versions support raw user ID based queries.
• Only version 11.0+ calls support ASID based queries.
• Version 11.0+ calls will receive ASIDs in responses, even when querying raw user IDs.

Time-based Pagination

Applies to v11.0+.
Added since and until parameters to the GET /{user-id}/media endpoint to support time-based pagination.

Instagram Graph API

Like Counts

Applies to v11.0+. Will apply to all versions September 7, 2021.
If indirectly querying an IG Media through another endpoint or field expansion, the like_count field will be omitted from API responses if the media owner has hidden like counts on it. Directly querying the IG Media (which can only be done by the IG Media owner) will return the actual like count, however, even if like counts have been hidden.

Time-based Pagination

Applies to v11.0+.
Added since and until parameters to the GET /{ig-user-id}/media endpoint to support time-based pagination.

Instant Experiences Templates

Applies to v11.0+.
Instant Experience Templates have moved out of of beta and are now available to all developers.

Messenger Platform

Messaging Postbacks Webhook

Applies to v11.0+.
The mid field has been added to the messaging_postbacks webhook to allow apps to get the Message ID.

Deprecation of Airline Templates

Applies to v11.0+. Will apply to all versions on Dec 6, 2021.
Calls to POST /{page-id}/messages that include any airline templates (template_type of types airline_boardingpass, airline_checkin, airline_itinerary, airline_update) will fail.

oEmbed

New oEmbed Read Feature

Applies to all versions.
The oEmbed product has been replaced with a new oEmbed Read feature. If you implemented the oEmbed product before June 8, 2021, you have until September 7, 2021 to complete App Review for the oEmbed Read feature. If you have not been approved for the oEmbed Read feature by September 7, 2021, your oEmbed implementations will fail to load.

Pages API

Comment IDs

Applies to v11.0+. Will apply to all versions on September 7, 2021.
The id field for comments will not be returned for any apps that only use the Page Public Content Access feature to query Pages endpoints. These include the id fields /PAGEPOST-ID/comments or /COMMENT-ID/comments. To get the id fields for comments for comments on Page posts the app user must be able to perform the MODERATE task on the Page being queried.

New Page Experience

Over the coming months, all classic Pages will be migrated to the New Pages Experience. Use the has_transitioned_to_new_page_experience Page field to determine if a Page has been migrated. After all Pages have been migrated, the classic Pages experience will no longer be available.
Most Pages API endpoints support both classic and NPE Pages. Endpoints that support NPE Pages display a "New Pages Experience" section in their references.
The following endpoints do not support NPE pages:

• /PAGE-ID/likes
• /PAGE-ID/global_brand_children
• /PAGE-ID/locations
• /PAGE-ID/tabs
• /PAGE-ID/visitor_posts
  Several Page fields are not available for NPE and will return null, a different data set or an error when called. Please visit our New Pages Experience Overview for a list of these Page fields.

Permissions user_likes

Applies to all versions.
The allowed usage for the user_likes permission has been updated. Starting September 7, 2021, apps that have already been approved for this permission but that violate its new usage description will have their approval revoked.

• Old allowed usage: Meaningfully improve the quality of a user's experience in your app (must be clear to the user how their data is used to provide that experience).
• New allowed usage: Provide a personalized experience by correlating or surfacing content related to the person’s likes. This includes curating content at scale to customize apps with large amounts of content and to enable people to share their likes with others, such as in the case of dating and music apps.

user_posts

Applies to all versions.
The allowed usage for the user_posts permission has been updated. Starting September 7, 2021, apps that have already been approved for this permission but that violate its new usage description will have their approval revoked.

• Old allowed usage: Meaningfully improve the quality of a user's experience in your app (must be clear to the user how their data is used to provide that experience).
• New allowed usage: Enable people to create physical or digital books or albums of their timelines, and to share memories from their timeline on Facebook or on other social apps.

SDK

Please visit the iOS SDK Changelog, Android SDK Changelog, and Unity SDK Changelog to learn about important upcoming changes to these SDKs.

Marketing API

Released June 8, 2021 | Available until February 23, 2022 | Blog post Audiences Custom Audiences, Lookalike Audiences, and Saved Audiences Deletion

Applies to all versions.
Beginning June 8, 2021 and going forward, any Custom Audience, Lookalike Audience, or Saved Audience that has not been used in any active ad set in over two years will be flagged as an "Expiring Audience". Then, the audience is scheduled to be deleted 90 days after being marked as an "Expiring Audience".
Developers will be able to filter for the "Expiring Audience" status using the operation_status field and see the audience's estimated time deletion in the system using the delete_time field. Developers can choose to either proactively delete the audience or use the audience in an active ad set to prevent deletion. Once an audience is deleted, advertisers will not be able to reactivate the audience.
For Custom Audiences (except Customer List Custom Audiences), Lookalike Audiences, or Saved Audiences:

• If advertisers wish for the flagged audiences to be automatically deleted beginning Sept 6, 2021 there is no action they need to take. However, if advertisers wish, they can also proactively delete the audience prior to the automatic deletion date.
• For flagged audiences advertisers wish to maintain, they should plan to use these in an active ad set prior to Sept 6, 2021 to prevent the audience from being deleted.
  For Customer List Custom Audiences:
• We store these on behalf of advertisers in accordance with their instructions. If advertisers do not take any action to use flagged audiences in an active ad set before Sept 6, 2021, we will consider this an instruction for us to delete the flagged audience.
  The following endpoints and fields will be affected:
• GET /{custom-audience-id}
• GET /act_{ad-account-id}/customaudiences?filtering
• GET /act_{ad-account-id}/saved_audiences?filtering
• GET /{saved-audience-id}
  See Audiences Overview: Custom Audiences Deletion Changes for more information on these updates.

Business API

Applies to all versions.
We are temporarily limiting access to the following endpoints. Only apps that have successfully called these endpoints within the last 30 days will continue to have access.

• POST /BUSINESS-ID/client_ad_accounts
• POST /ADACCOUNT-ID/agencies
  All other apps will receive an error when making calls to these endpoints.

Catalog API Deprecation of Product Inventory Field

Applies to 11.0+.
The inventory field will be deprecated and replaced with a new quantity_to_sell_on_facebook field. While we will continue to support the inventory field for the near term, we recommend that you use the new quantity_to_sell_on_facebook field instead.
The following endpoints are affected:

• GET /{product-item-id}
• GET /{catalog-id}/products
• POST /{product-item-id}
• POST /{catalog-id}/items_batch
  See Quantity to Sell and Supported Fields for Products - Dynamic Ads & Commerce for more information on this update.

Deletion of Non-Empty Product Groups

Applies to 11.0+. Will apply to all versions on Sept. 7, 2021.
We will no longer allow deletion of non-empty product groups by default. Non-empty product groups can be deleted by applying deletion_method=delete_items to the deletion request. This will delete both the product group and its items.
The following endpoint is affected:

• DELETE /

Deletion of Live Product Sets

Applies to 11.0+. Will apply to all versions on Sept. 7, 2021.
We will no longer allow deletion of a catalog with live product sets by default. To enable deletion of a catalog that contains a live product set, set the catalog's allow_delete_catalog_with_live_product_set parameter to true.
This change affects the following endpoint:

• DELETE /

New Diagnostics Endpoint

Applies to 11.0+.
We have added a new endpoint GET /{product_catalog_id}/diagnostics. This endpoint can be used to retrieve diagnostics data for a given catalog, such as issues that prevent products from showing in channels and opportunities that could improve product discoverability.

Commerce API Order Total Estimated Payment Details

Applies to 11.0+. Will apply to all versions on Sept. 7, 2021.
We are changing the way estimated payment details are reported in order totals for calls to the {commerce-order-id}/?fields=estimated_payment_details endpoint. Previously, if an order was not fulfilled, an estimated tax was used, and for fulfilled orders, the fulfilled tax was used. Starting with version 11.0, this endpoint will always use the estimated tax. Note that details about the fulfilled tax can be accessed using {commerce-order-id}/items?fields=tax_details.

Conversion Lift Metrics Changes

Applies to v11.0+. Will apply to all versions on Sept. 7, 2021.
Metrics returned from the GET /{objective-id}/?fields=result field have changed.
The following metrics have been added:

• conversions_incremental_share
• conversions_CPiC
• conversions_multicell_confidence
• conversions_multicell_rank
• sales_incremental_share
• sales_multicell_confidence
• sales_multicell_rank
• buyers_incremental_share
• buyers_CPiB
• buyers_multicell_confidence
• buyers_multicell_rank
  The following metrics have been removed:
• advancedBuyers.control
• ancedBuyers.informativeMultiCellBayesianConfidence
• advancedBuyers.lift
• advancedBuyers.test
• advancedConversions.control
• advancedConversions.informativeMultiCellBayesianConfidence
• advancedConversions.lift
• advancedConversions.test
• advancedSales.control
• advancedSales.informativeMultiCellBayesianConfidence
• advancedSales.lift
• advancedSales.test
• buyers.baseline
• buyers.bayesianCILower
• buyers.bayesianCIUpper
• buyers.control
• buyers.delta
• buyers.incremental
• buyers.isStatSig
• buyers.lift
• buyers.multiCellBayesianConfidence
• buyers.reachedPercent
• buyers.singleCellBayesianConfidence
• conversions.baseline
• conversions.bayesianCILower
• conversions.bayesianCIUpper
• conversions.control
• conversions.delta
• conversions.incremental
• conversions.isStatSig
• conversions.lift
• conversions.multiCellBayesianConfidence
• conversions.reachedPercent
• conversions.singleCellBayesianConfidence
• frequency
• incrementalROAS
• sales.baseline
• sales.bayesianCILower
• sales.bayesianCIUpper
• sales.control
• sales.delta
• sales.incremental
• sales.isStatSig
• sales.lift
• sales.multiCellBayesianConfidence
• sales.singleCellBayesianConfidence
  The following metrics have been renamed:
  Old Name | New Name
  advancedBuyers.baseline | buyers_not_exposed
  advancedBuyers.bayesianCILower | buyers_incremental_lower
  advancedBuyers.bayesianCIUpper | buyers_incremental_upper
  advancedBuyers.incremental | buyers_incremental
  advancedBuyers.informativeMultiCellPairwiseBayesianConfidence | buyers_multicell_confidence
  advancedBuyers.informativeSingleCellBayesianConfidence | buyers_confidence
  advancedBuyers.scaled | buyers_control_scaled
  advancedConversions.baseline | conversions_not_exposed
  advancedConversions.bayesianCILower | conversions_incremental_lower
  advancedConversions.bayesianCIUpper | conversions_incremental_upper
  advancedConversions.incremental | conversions_incremental
  advancedConversions.informativeMultiCellPairwiseBayesianConfidence | conversions_multicell_confidence
  advancedConversions.informativeSingleCellBayesianConfidence | conversions_confidence
  advancedSales.baseline | sales_not_exposed
  advancedSales.bayesianCILower | sales_incremental_lower
  advancedSales.bayesianCIUpper | sales_incremental_upper
  advancedSales.incremental | sales_incremental
  advancedSales.informativeMultiCellPairwiseBayesianConfidence | sales_multicell_confidence
  advancedSales.informativeSingleCellBayesianConfidence | sales_confidence
  advancedSales.scaled | sales_control_raw_scaled
  buyers.pValue | buyers_raw_pValue
  buyers.reached | buyers_exposed
  buyers.scaled | buyers_control_raw_scaled
  buyers.test | buyers_test
  conversions.pValue | conversions_raw_pValue
  conversions.reached | conversions_exposed
  conversions.scaled | conversions_control_raw_scaled
  conversions.test | conversions_test
  IncrementalROAS | sales_ROAS
  sales.pValue | sales_raw_pValue
  sales.reached | sales_exposed
  sales.scaled | sales_control_raw_scaled
  sales.test | sales_test
  A complete list of the available metrics can be seen in the Facebook Lift Metrics Glossary.

Insights API

Deprecation of Store Visit Metrics

Applies to 11.0+. Will apply to all versions on Sept. 6, 2021.
The store_visits_actions and cost_per_store_visit_actions metrics are deprecated.
The following endpoints are affected:

• GET /{adaccount-id}/insights
• GET /{campaign-id}/insights
• GET /{adset-id}/insights
• GET /{ad-id}/insights
• POST /{adaccount-id}/insights
• POST /{campaign-id}/insights
• POST /{adset-id}/insights
• POST /{ad-id}/insights

Offer Ads API

Deprecation of Offer Ads API Endpoints

Applies to v11.0+. Will apply to all versions on Sept 7, 2021.
As part of our ongoing effort to increase product stability, Facebook will be ending its support for our Offer Ads product on June 8, 2021. Standard Facebook Ads are the recommended substitute for distributing your in-store and or online discounts. Discount information, redemption location(s), expiration date, and promotional codes are advised to be placed directly in the Ad Level creative.
The following endpoints are deprecated:

• GET /{page-id}/nativeoffers
• POST /[page-id}/nativeoffers
• GET /pagename/nativeoffers
• GET /{native-offer-id}
• GET /{native-offer-id}/views
• POST /{native-offer-id}/codes
• POST /{native-offer-id}/nativeofferviews
• GET /{offer-id}/comments
• GET /{offer-id}/sharedposts
• GET /{offer-id}/likes

Original source

Graph API

Released February 23, 2021 | Available until June 8th, 2023 | Blog post

Business Apps

Access Levels

Applies to all apps created after February 16, 2021.
All Business type apps created after February 16, 2021 will automatically be granted Standard access to the email and public_profile permissions.
Applies to all existing apps created after February 16, 2021.
All Business type apps created before February 16, 2021 will automatically be granted Advanced access to the email and public_profile permissions. Apps that are not using the email or public_profile permissions will be downgraded to Standard access for these two permissions.
Business type apps can upgrade to Advanced access for the email and public_profile permissions without going through App Review.

Groups

Applies to v10.0+. Will apply to all versions on May 25, 2021.

• To align with other Facebook data retention policies, the Groups API will only include data created within the last 90 days of your queries. The data returned is dependent on the access level or mode of your app and your role on the app.
• Groups API will now use a 2 tiered API access level system, Standard level and Privileged level, instead of Dev mode and Live mode access. Standard level access will only allow you to get data for users that have a role on your app, while Privileged level access will allow you to get data from all users in the group that the app is installed in.

Pages

Reinstated endpoint
Applies to v10.0+. Will apply to all versions on May 25, 2021.
The DELETE /{page-id}/tabs endpoint that was deprecated in v8.0 has been reinstated in v10.0 and will be reinstated in all versions on May 25, 2021.

Threat Exchange

Deletion of expired data
Will apply to all versions on May 25, 2021.
Data uploaded to ThreatExchange with a non-zero expire_time will be permanently deleted at the expiration time indicated. If you wish to delete data that is no longer valid, set the expired_on field to the current time to have the data deleted immediately.
Additionally, all non-Facebook ThreatDescriptors will be permanently deleted once they reach the expiration date set by the creator. If your application currently has expired ThreatDescriptors that you don’t want deleted, you must extend the expiration date or set it to ‘0’ to ensure that the data never expires.

URL

Applies to v10.0+. Will apply to all versions on May 25, 2021.

Engagement

• Due to privacy concerns, counts returned by a GET /?id={url}/engagement request may not match raw counts.
• Requests for the GET /?id={url}/engagement field for the same URL will be limited to 10 requests per hour.

Marketing API

Released February 23, 2021 | Available until October 4, 2021 | Blog post

Ad Account

Field changes
Applies to v10.0+. Will apply to all versions May 25, 2021.
The agency_client_declaration field on the AdAccount node now requires Admin privileges for all operations.

Ads Insights API

Updated date_preset parameter
Applies to v10.0+.

• The lifetime parameter (date_preset=lifetime) is disabled and replaced with date_preset=maximum, which can be used to retrieve a maximum of 37 months of data. The API will return an error when requests contain date ranges beyond the 37-month window.
• For v9.0 and lower, there will be no change in functionality until May 25, 2021. At that time, date_preset=maximum will be enabled and any lifetime calls will default to maximum and return only 37 months of data.

Business

Easing of Previous Endpoint Access Restrictions

Applies to 10+.
In v9.0, access to the endpoints below was restricted. Access has been restored to all apps, but apps can now only target businesses (or child businesses of those businesses) that have claimed them:

• POST //access_tokens
• POST /{business-id}/business_users
• POST /{business-id}/system_users

Targeting

Connections Targeting

Will apply to all versions May 24, 2021.
The following endpoints will no longer accept connections targeting when creating or editing ad campaigns:

• POST //adsets
• POST /
  This change will not affect any existing running campaigns.

Lookalike Audiences

UPDATED APRIL 28, 2021: The removal of the location_spec and country parameters from lookalike audience creation is currently delayed. Updates on when this change will go into effect will be forthcoming.
The location_spec and country parameters will be removed from lookalike audience creation. The location for the lookalikes will be defined by the country location in the campaign’s targeting specification.
There will be no impact on existing campaigns given this change. This requirement will only impact new and edited campaigns.
The following endpoints and fields will be affected:

• POST //customaudiences
• POST //adsets
• POST //adaccounts?adaccounts=
• GET //reachestimate
• GET //delivery_estimate
• GET /?fields=approximate_count
• GET /?fields=delivery_status
• GET /?fields=operation_status
  See Lookalike Audiences: Upcoming Lookalike Changes for more information on these updates.

Original source