Version 12.0

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:


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.


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

Applies to v12.0+. Will apply to all versions TBD.

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:


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 TBD | 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:

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.


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:

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: