Released October 8, 2025 | Available until TBD | Blog post
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.
The overlay_url field on the GET /<LIVE_VIDEO_ID> 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.
See the WhatsApp Business Platform changelog.
Released October 8, 2025 | Available until TBD | Blog post
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:
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}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:
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 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:
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:
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:
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:
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:
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:
allow_upsertApplies 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:
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:
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:
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