Graph API
Zurück zu Deutsch
Dieses Dokument wurde aktualisiert.
Die Übersetzung ins Deutsche ist noch nicht fertig.
Englisch aktualisiert: 30.08.2019
Deutsch aktualisiert: 02.08.2018

Version 2.6

Graph API | Marketing API

Einträge im Änderungsprotokoll sind in die folgenden Kategorien unterteilt:

  • Neue Funktionen: Neue Produkte oder Dienste, z. B. neue Nodes, Edges und Felder.
  • Änderungen: Änderungen an bestehenden Produkten oder Diensten (dazu gehören nicht veraltete Elemente)
  • Veraltete Elemente: Bestehende Produkte oder Dienstleistungen, die entfernt werden.
  • Funktionsgefährdende Änderungen nach 90 Tagen: Änderungen und veraltete Produkte, die 90 Tage nach dem Veröffentlichungsdatum der Version in Kraft treten werden.

Neue Funktionen, Änderungen und Veraltete Elemente betreffen nur diese Version. Funktionsgefährdende Änderungen nach 90 Tagen betreffen alle Versionen.

Funktionsgefährdende Änderungen werden hier nicht aufgeführt, da sie nicht an bestimmte Veröffentlichungen gebunden sind.

Graph API Version 2.6

Released April 12, 2016 | Available until July 13, 2018

New Features

Pages

  • Notes on Users - Page admins can take notes on Users. Please see the admin_notes edge reference docs on the Page node for more information.
  • Labels on Users - Page admins can create labels for Users. Please see the labels edge reference docs on the User node for more information.
  • Send Messages to Users Using Page-Scoped ID or Phone Number - Pages can now send text, attachments, and template messages to users through their page-scoped-ids or phone numbers.
    • The pages_messaging permission to send and receive messages on behalf of a Page.
    • The pages_messaging_phone_number permission to send messages on behalf of Pages using a phone number as an ID.

Video APIs

  • Live API - Post and manage Live Videos. Access to these endpoints requires approval. Please see our Live API documentation for more information.

  • Video Node - The following fields have been added. Please see the Video node reference docs for more details.

    • live_status. The current broadcast state of the video. Values include: LIVE, LIVE_STOPPED, VOD. If this field is null, it means the video was never broadcast.
    • live_audience_count - The number of unique viewers who watched the video when it was live.
    • content_tags - Add tags to a video.
  • Rights Manager API - We've introduced a new Rights Manager API that allows a copyright owner to claim ownership for videos and manage copyright matching rules. To use the API, please enroll via the Rights Manager Enrollment website. Please see our documentation for the Rights Manager API for more information about the API and the enrollment process.
  • Crossposted Videos - Pages can now create posts from videos they own without the need to re-upload the videos again. The major benefit of this is that you can see consolidated insights for a video and a breakdown of metrics across the multiple posts created from the video. Please see the is_crossposting_eligible and crossposted_video_id field in the Video node and the videos_you_can_use field on the Page node for more information. The videos_you_can_use field tells you if a Page owner has granted permission for you to cross-post it

  • Video Insights - The following edge has been added to the Video node:

    • video_insights - Contains aggregated video insights from all crossposts across Pages. See the video_insights edge for more information. We have also added Daily Video Metrics, Minutes Watched, and 10s metrics to insights edge on the Post Node.

Messenger APIs

  • Webhooks - The following fields have been added. Please see our implementation guide for more information.

    • messages - Receive inbound messages.
    • message_deliveries - Receive delivery confirmations.
    • messaging_optins - Receive authentiation events.
    • messaging_postbacks - Receive postback from buttons on Structured Messages.

  • Messenger Plugin - We've added a new web plugin to authenticate people into the Messenger Platform. People can now interact with your business over Messenger. Please see our implementation guide for more information.

  • Message Us Plugin - We've added a new web plugin to enable people to start a chat directly with a Page. Please see our implementation guide for more information.

  • Send/Receive API - The Send/Receive API is part of the Messenger Platform. It can be used to send and receive messages between people and Pages. Please see our implementation guide.

Sharing for Devices

  • Sharing for Devices - We're launching a new Sharing for Devices API that lets you share easily from a device to Facebook. Please see our documentation on Sharing for Devices for more information.

Photos

  • Reactions API - We've added a new reactions edge for objects that were previously likable. As an example, please see the Photo edge for reactions.

Changes

Pages

  • The likes field on the Page node has been renamed to fan_count.
  • You can no longer login as a Page. Please see our Pages documentation to learn more about posting as a Page.

Deprecations

6 Month Deprecations

  • Feed Dialog - Applications using the Feed Dialog will be required to have the publish_actions permission to have access to the returned post_id. The post_id will only be returned if the share generates a story on a person's timeline or in a group. This will take effect on October 11th.

Apps

  • Insights - The following metric has been deprecated:

    • facebook_login_total_users

Devices

  • Device Authentication - The following endpoint has been deprecated:

    • oauth/device - This affects devices that use this endpoint to generate access tokens. Please use the device/login and device/login_status endpoints instead. See our documentation on logging in with devices for more information.

Pages

  • The following Pages Insights have been deprecated. Each of these has been replaced by another way to query a similar set of insights. Please see our documentation on Page Views for more information. The new insights start with the page_views prefix.

    • page_visits_by_age_gender_logged_in_unique
    • page_visits_by_internal_referer_logged_in_unique
    • page_visits_by_profile_tab_logged_in_unique
    • page_visits_by_profile_tab_total
    • page_visits_by_site_logged_in_unique
    • page_visits_logged_in_total
    • page_visits_logged_in_unique
    • page_visits_total

Breaking Changes

Apps

  • Role Visibility - Starting with the release of v2.6, an application can no longer see all of the roles that a developer has on other apps. This change also applies to previous versions.

Games

  • Game Groups Beta - The Game Groups Beta feature, also known as App Groups, is deprecated as a 6 month deprecation. Effective May 1, no new apps may use the Game Groups API. Final deprecation effective on October 18th.

90-Day Breaking Changes

Pages

  • Rate Limits Changes for Page-related Requests - If you make a request with a Page Access Token, the limits will scale with the number of people engaging with the page. This change will take effect July 11th.

Webhooks

  • All Callback Subscriptions Must Use HTTPS - When we launched Graph API v2.5 last October we began requiring new Webhooks (formerly known as Real Time Updates) subscriptions to be configured for HTTPS. With v2.6, this is now required for all new Dynamic Pricing and Deauthorization endpoints as well. Beginning 90 days from today, we will require all callback subscriptions to be configured for HTTPS. At that point, we will stop sending updates to non-HTTPS endpoints, regardless of when they were created. This applies to Webhooks, Webhooks for Payments, Dynamic Pricing, and Deauthorization. You can update your subscriptions on your app dashboard.

Marketing API

Released April 12, 2016 | Available until October 5, 2016

New Features

  • No New Features.

Changes

Ads Management

  • Deprecated the connectionobjects API which retrieved all object types and replace it with other APIs that return specific object types. This greatly improves the performance and maintainability. More details here. The new API is at these endpoints:

    • Pages: user_id/accounts
    • Events: user_id/promotable_events
    • Apps: adaccount_id/advertisable_applications
    • Domains: user_id/promotable_domains
  • Sharing a Custom Audience (CA) to Ad Accounts can be done through <CUSTOM_AUDIENCE_ID>/adaccounts API. When a custom audience is shared to a AdAccount, there is a permission setting for sharing it with targeting only or with targeting_and_insights option. Targeting means a recipient ad account can target ads to the audience, insights means the recipient ad account can also use insights tool to view the audience demographics. The default has changed from targeting only to targeting_and_insights in 2.6.

Dynamic Ads

  • Changed Product Catalog Sales Objective ad set's default optimization_goal to OFFSITE_CONVERSIONS.

  • Default to carousel format. In order to opt-out of carousel format, specify force_single_link=true in object_story_spec.

  • Return an error if no username/password provided for (S)FTP urls when scheduling the product feed. Empty username/password is allowed. e.g. username:"".

Insights

  • Changed the default for date_preset value from lifetime to last_30_days and fields value from all fields to impressions,spend. Both of these defaults apply to /insights for all object levels.

  • The fields parameter no longer accepts breakdowns such as age or gender. Now you should specified this in breakdowns parameter in query. This includes: age, country, gender, frequency_value, hourly_stats_aggregated_by_advertiser_time_zone, hourly_stats_aggregated_by_audience_time_zone, impression_device, place_page_id, placement, product_id, and region. This applies to /insights for all object levels.

  • Ads Insights API will throw error if since specified in time_range is in the future. Also replace until by today if until is in the future.

Lead Ads

  • When querying to retrieve qualifier information for a Lead Ads form, the label and question values of the qualifier are interchanged for Custom Questions. We are fixing this so that moving forward content under label and question will be returned correctly.

Targeting

  • The user_device field is changing to a new format. The old format contains underscores combining brand and marketing name, like ['samsung_galaxy_s6']. The new format contains the device marketing name only, like ['galaxy s6']. Valid values can be retrieved from /search?type=adTargetingCategory&class=user_device. All read requests will be automatically transformed to new format. All writes require the new format.

    • Note that because the values for user_device are different, /reachestimate calls must be made to an object's corresponding version. For example, if an ad set was created in version v2.5 while targeting user_device using the old format, the /reachestimate call for that ad set will return inaccurate values unless it's also made under v2.5.

Deprecations

Dynamic Ads

  • The following fields have been deprecated:

  • product_ad_behavior field at the Ad Set level, which is used by Dynamic Ads. Instead we now default all new Ad Sets to FALL_BACK_TO_FB_RECOMMENDATIONS. That means Facebook will automatically choose the highest-performing products from the creative's Product Set to show people who have browsed products that are not in the Product Set.

  • {page_id}/rtb_dynamic_posts for DPA. Use [<OBJECT_STORY_ID>]/dynamic_posts instead.

  • max_product_count since Facebook now automatically optimizes the number of products to show for Dynamic Product ads. In order to opt-out of carousel format, specify force_single_link=true in object_story_spec.

  • row_number and column_number fields on product feed upload error /<UPLOAD_ID>/errors, they are available on error samples now.