Released September 14, 2021 | Available until TBD | Blog post
Applies to v12.0+.
The App Insights API is deprecated. Affected endpoints:
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
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
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:
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.
Applies to v12.0+.
Added two new fields to the GET /{video-id}
endpoint:
post_views
views
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
Released September 14, 2021 | Available until August 9, 2022 | Blog post
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:
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.
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.
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
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.
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"]
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: