Released October 7, 2015 | Available until April 12, 2018
This version expired April 12, 2018. Please use the API Upgrade Tool to upgrade your apps before this date. Learn more about upgrading your apps in the Upgrade Guide.
Permissions
GET {user_id}/accounts
now requires either manage_pages
or pages_show_list
; the latter is a new permission in v2.5.POST {page_id}/call_to_actions
and POST/DELETE {call-to-action-id}
require the new permission pages_manage_cta
that we introduce in v2.5.Managing Call-to-Actions - Pages can now manage call to actions on a Page:
GET page/call_to_actions
or GET {call-to-action-id}
to read a call to action.POST page/call_to_actions
to add a call to action to a page.POST {call-to-action-id}
to update. DELETE {call-to-action-id}
to delete a Page's call to action.Place Node - The following field has been added to the Place
node:
overall_rating
- This provides the average rating based on public reviews of a place.Video Upload - The following parameters have been added:
slideshow_spec
- Generate slide show videos by uploading images.secret
- Published video will not appear on Facebook Newsfeed, Timeline, or Page video tabs and is not searchable. A video can be viewed and shared using a permalink only. For page users only. social_actions
- Enable or prohibit the use of Facebook social actions such as likes, comments, and sharing on an hidden video. For page users only. Video Editing - The following parameters have been added:
publish_to_videos_tab
- Distribute video items publicly to the Page's Videos tab, but not News Feed or Timeline.publish_to_news_feed
- Distribute video items publicly to News Feed, Page Timeline, and a Page's Videos tab.GET /{page-id}/tagged
will include all public posts in which the page has been tagged. A page access token with manage_pages
permission is required.story_tags
- Now returns an array, not an object.GET /{user-id}?fields=address
returns an error - The address
field, which was available in previous versions and returned an empty value, will return an error as of v2.5.Automatically Disable Subscriptions - We now automatically disable Webhooks subscriptions if the callback URL fails for 7 days straight. You can re-enable it with a POST
request to /subscriptions
. This change does not apply to payments subscriptions.
Updating Existing Subscriptions - Existing Webhooks subscriptions may be modified via the /subscriptions
API. POST /subscriptions
will amend the subscription for the given topic without overwriting existing fields. You can delete specific fields from your subscription by including a fields param when calling DELETE /subscriptions
.
https://www.facebook.com/{vanity}?v={app_id}
will no longer work 90 days after this release. Please use https://www.facebook.com/{vanity}?sk={app_id}
or https://www.facebook.com/{vanity}/{app_id}
.User
, Page
, App
, and Payment
updates.Released October 7, 2015 | Available until July 13, 2016
Ad, Ad set, and Campaign object read path additions:
effective_status
to reflect the real Ad delivery status. For example for an active adset in a paused campaign, the effective_status
of this adset is CAMPAIGN_PAUSED
.configured_status
to reflect the status specified by user. Insights - The following metrics have been added:
inline_link_clicks
cost_per_inline_link_click
inline_post_engagement
cost_per_inline_post_engagement
Admin Name - Default the name
of the first visible admin to current user if not specified.
Campaign -The following objective names have changed:
WEBSITE_CLICKS
to LINK_CLICKS
WEBSITE_CONVERSIONS
to CONVERSIONS
DPA - Enforce Terms of Service for all Product Catalogues and Dynamic Product Ads users. Advertisers implicitly accept by creating their first catalog through Business Manager. For API developers, Terms of Service need to be accepted through BM when the product catalog is first created.
Local Awareness Ads
- Require
page_id
inpromoted_object
at the/adset
level for Local Awareness Ads- No longer require
custom_locations
for location targeting, and also allow sub-national, single country targeting. Now all location types (except for country) must be within the same country.
- Change
/adcampaign_groups
to/campaigns
- Change
/adcampaigns
to/adsets
- Change
/adgroups
to/ads
- In the write path, change campaign_group_status, campaign_status, adgroup_status to
status
- Response for call to
/search?type=adgeolocation
will contain only the 'City' instead of 'City, State'- Change
{cpc, cpm, cpa}_{min, max, median}
, such ascpc_min
fields in /reachestimate tobid_amount_min
,bid_amount_median
,bid_amount_max
. Changebid_for
tooptimize_for
- Remove
friendly_name
- Remove
USE_NEW_APP_CLICK
- Remove
buying_type
- Remove ability to create campaign with
Objective='NONE'
. 'NONE' is still a valid read-only objective. You can continue to edit existing campaigns.- Remove
REACHBLOCK
,DEPRECATED_REACH_BLOCK
from campaignbuying_type
. For older campaigns using these twobuying_type
, the API will returnRESERVED
forREACHBLOCK
andFIXED_PRICE
forDEPRECATED_REACH_BLOCK
.FIXED_CPM
is replaced withFIXED_PRICE
.
- Remove filter on
adgroup_id
,campaign_id
, orcampaign_group_id
. Instead usead.id
,adset.id
andcampaign.id
- Note Prior to 2.6 We decided to extend the timeline to deprecate Clicks(All) and CPC metrics until the deprecation of API v2.6. In 2.5, removed
cpc
andclicks
fields in Insights API. Newly added related metrics includeinline_link_clicks
,cost_per_inline_link_click
,inline_post_engagement
,cost_per_inline_post_engagement
. Please note clicks(all) historically counted any engagement taken within the ad unit as a click. Thus, clicks(all) won't be a simple addition oflink_clicks
andpost_engagement
. The newly added fields are available in v2.4 and v2.5.
Reach Estimate - Require optimize_for
at the /reachestimate
endpoint.
Targeting
- Remove
want_localized_name
param for/search?type=adgeolocation
.- Remove
/search?type=adcity
andadregion
, use/search?type=adgeolocation
instead.- Remove
engagement_specs
andexcluded_engagement_specs
from targeting spec. The similar video remarketing functionality is supported through/customaudiences
endpoint.Deprecate or make private certain targeting options:
- Instead of being returned in
/search
, private categories will now be returned in/act_{AD_ACCOUNT_ID}/broadtargetingcategories
or/act_{AD_ACCOUNT_ID}/partnercategories
.- Deprecated categories will no longer be returned.
- Updates to ad set targeting using private or deprecated categories will error. It's recommended to query the validation endpoint before updating the ad set targeting to identify which targeting options to remove.