换季衬衫做外套 学井柏然内搭T恤至少20种穿法

百度 在全球要素与重大利益关系上，中国和美国之间的利益诉求共同点会越来越多；但在具体产业之间，中美横向关系的竞争会越来越激烈。

This document contains the changelog for versions of the Messenger Platform that are no longer supported.

The latest version is: v23.0

Related Changelogs

• Graph API Changelog
• Instagram Graph API Changelog
• Marketing API Changelog
• Messenger Platform Changelog

Aug 04, 2020 - V8.0

• Introducing updates to the Facebook Chat Plugin (formerly known as the Customer Chat Plugin) – Today, we are introducing a new and improved design, and the Chat Plugin now connects businesses to all users on their websites, even if they are not logged into Facebook. To ensure optimal user experience, we recommend that developers read the new webhooks that detect if a user is messaging the business in guest mode, and when the guest session is terminated.
• Shops API - We are launching support for sending and receiving products on Messenger for Shops. This includes the Product Template that can be used to send products in messages, product details page (PDP) referral info in message webhook, Product XMA support in Conversation API, webhooks for messages with product template and messages from Facebook Shops Product Detail Page, and echo webhooks for messages with products.
• App Review Submission Changes - We have merged the Messenger app review process with the main app review and provided instructions in a sample submission.

The following changes take effect on v8.0+ today and will affect all versions on Aug 4, 2022

• Nested Persistent Menu - Messenger Profile API and Customer User Settings API will not support nested menus on v8.0 and above. Additionally, these APIs will allow creating flat (single level) menus with up to 20 items. The latest Android app will flatten nested menus, just as the iOS app does.
• Thread Settings API - Thread Settings API was replaced by Messenger Profile API in 2017. It will not be available on v8.0 and above.

May 05, 2020 - V7.0

The following changes take effect on v7.0+ today and will affect all versions on November 2nd, 2020

• Customer Chat Plugin Webhooks - When a new conversation is started or an existing conversation continued via the Customer Chat Plugin, the webhook events messaging_postbacks and messaging_referrals will include a user_ref instead of PSID until the user sends a message.

The following changes take effect on v7.0+ today and will affect all versions on May 5, 2022

• Messenger Profile API - getting, setting or deleting home_url is no longer supported. This parameter was used for a previously deprecated feature (Chat Extensions).

March 04, 2020

• Introducing Messenger Webhook Versioning - Allowing a window for developers to opt-in into platform changes affecting webhooks. Version changes can be done live and rolled back if needed to promote smooth migrations.
• Update on Share to Messenger SDK - Last June, we announced plans to no longer support the Share to Messenger SDK. We are excited to share that we will continue to support a modified version of the Share to Messenger SDK, which will allow people to share links and photos from your app to Messenger. The support for link and image/video sharing on the iOS Messenger app will be rolled out gradually over the next few weeks. We will no longer support sharing generic and media templates. If you still have the SDK in your app, no action is required.
• Policy Enforcement - The updated Messenger Platform Policy is in effect starting today.

The following changes apply for v6.0+

• Webhook Event messages - Adjusted the way attachments type fallback and image with a sticker are sent.

February 04, 2020 - V6.0

• One Time Notification API (beta) - As promised in our Dec 20th announcement, we are rolling out the beta for One Time Notification API today. This will allow Users to give Pages the permission to send a future notification message outside of the 24 hour response window.

The following APIs are deprecated on v6.0+ and will be removed from all versions on June 30, 2020

• Sending Messages through Conversation API - This legacy endpoint is being deprecated in favor of the more feature rich Send API. Developers have until June 30, 2020 to update their apps before this functionality breaks on all versions of the API.

The following APIs are deprecated on v6.0+ and will be removed from all versions on May 4, 2020

• Page Message Tags API - As we have simplified and reduced the number of our message tags, it is recommended to hard code them in your app.
• User Threads API - Note that this reference page is available only to apps on v4.0 or before.

December 20, 2019

Today, we are sharing a new effective date for the policy changes that we announced on August 29, 2019 to give developers and businesses additional time to prepare for the policies and incorporate new messaging features. The new policy will now go into effect on March 4, 2020. For more details, see the Messenger Platform Policy Overview

The breaking change announced on October 29, 2019 affecting Broadcast API and Legacy sponsored messages has been set for March 4, 2020.

Based off feedback from our community, we identified additional use cases aligned with our policy principles that were not covered under the original set of message tags. Thus, we are planning to introduce a “one-time notification” API in February.

For more details, see Listening to our Community: Messenger Provides More Time to Adapt to New Policies and Announces One-time Notification API

December 04, 2019

• User Level Persistent Menu - We are making it easier for businesses and developers to personalize conversational experiences at the user level on Messenger. Taking this feature out of closed beta into general availability.
• Helper Webhooks for user reactions and message replies - We added a temporary toggle that allows apps created before this date to opt in into human readable descriptions of replies and reactions to help apps show them to agents without code changes.

The following breaking change date is adjusted to June 30, 2020, the features described below remain deprecated.

• read_page_mailboxes used in Conversation API and Legacy Private Reply, deprecated in favor of the pages_messaging permission.
• The Pages webhook field conversations is deprecated. Please migrate to use the messages webhook field supported in Messenger platform instead.

October 29, 2019 - V5.0

• Handover protocol improvements for click to Messenger ads - We are making it easier for businesses that have multiple apps connected to the Messenger platform to dynamically select the app that they want to use for their click to Messenger ads.
• Ice Breakers - Ice Breakers help businesses reduce friction in starting a conversation by surfacing common questions or topics of interest. Businesses can now set icebreakers on their Messenger profile via the API.
• Webhooks for user reactions and message replies - It is now possible to receive webhook events when users react or reply to messages from businesses.
• Filter for admin text - Admin texts are messages sent by Messenger during conversations between people and businesses. We are now adding a filter to the thread API to allow apps to request messages without them.

The following APIs are deprecated on v5.0+

• Legacy private reply - Please use the new private reply via Send API.

The following APIs are deprecated on v5.0+ and will be removed from all versions on March 4, 2020 (Updated on December 20, 2019)

• Broadcast API - Use the Send API to send messages
• Legacy Messenger platform sponsored messages - We recommend using the fully featured Meta's Marketing API for sponsored messages. The Marketing API also provides an API to estimate delivery and insights API to get ad impression data.

September 30, 2019

• User Level Persistent Menu - We are making easier for businesses and developers to personalize the conversational experience at the user level on Messenger. With this beta, apps will be able to dynamically change the persistent menu and the visibility of the composer.
• Private Replies - We made improvements to private replies. The old Private Replies only allowed plain text to be sent. With this update businesses can send images, templates and quick replies as part of the message they send in response to a post or comment on their Page.
• URL Buttons have App Link Support - We are improving the mobile integration capabilities in Messenger by introducing App Link support for URL buttons. This will allow developers and businesses to provide a button that can click into a native app.
• Changelog Notifications - Developers can now subscribe to email notifications of changes in this changelog.

August 29, 2019

Policy Update

The Messenger Platform’s policies are designed to help people and businesses connect in ways that drive meaningful outcomes. At the heart of this is the understanding that people and businesses need a seamless, reliable way to get something done - whether it is getting a question answered, making a purchase, or communicating important and relevant updates. The following policy update is designed to make communication between people and businesses on Messenger relevant, important and timely.

Apps have until March 4, 2020 (Updated on December 20, 2019) to migrate to the new policy. We highly encouraged developers to adopt these policies right away to ensure a smooth transition. See Messenger Platform Policy Overview

Effective March 4, 2020 (Updated on December 20, 2019).

• Revised Standard Messaging Window Policy: We are updating our policies to a 24-hour standard messaging window. We know that people expect businesses to respond quickly and, not surprisingly, businesses that respond in a timely manner to achieve better business outcomes. To improve the people to business experience, businesses will no longer be able to send a message outside the 24-hour window as part of the standard messaging window policy.
• Introducing More Streamlined Message Tags: We are simplifying message tags. Message tags enable businesses to send personalized, 1:1 messages to people outside of the standard messaging window. Message tags are now available for the following use cases: post-purchase updates, event reminders, and account updates, and human agent (closed beta).
• Effective Audience Reengagement Outside 24-Hour Message Window: Businesses who want to send one message to many people, which may include promotional content, outside the standard messaging window, have the opportunity to use sponsored messages. Sponsored messages are a great way for businesses to re-engage people who currently have an open chat with the business.
• Subscription Messaging Beta Update: We are updating this policy as we found some businesses were using the subscription messaging beta in ways that weren’t in line with our policy and led to a poor experience for people and other businesses. Moving forward, subscription messaging will only be available for news organizations who successfully register their Pages through the Facebook News Page Index to help improve the user experience and business outcomes.

For more details, see the Messenger Platform Policy Overview

Discovering Businesses on Messenger As a part of our continued commitment to simplify the Messenger experience for people, we are removing the Discover tab from the Messenger app. We will continue to invest in more and better ways to help businesses connect with their customers wherever they are, including updates to m.me links, various entry points across our family of apps, as well as ad products that lead to Messenger.

July 29, 2019 - V4.0

• M.me links now reopen the 24hr window within existing threads. When a person clicks an m.me link that contains a ref parameter and is taken into an existing thread, it will now reopen the 24hr standard messaging window. This will allow apps powering Pages to reply to people based on the context that the ref parameter provides.
• Messenger rate limit - The new rate limit is now tied to the number of people a Page can send messages to. Enforced on v4.0+ and will apply to all versions on October 29, 2019.

The following APIs are deprecated on v4.0+

• Vertical List Template
• Open Graph Template
• broadcast_messages
• broadcast_reach_estimations

Breaking Changes

The following APIs are deprecated on v4.0+ and will be removed from all versions on October 29, 2019

• Location Quick Reply Button
• Messenger Share Button
• Messenger Codes API

June 10, 2019

During F8 2019, we announced our plans to launch a lighter, better and simpler Messenger designed to build closer connections between people and businesses. Starting August 15, 2019, updated versions of the Messenger app will reflect the following changes:

Won't render on the new app

• Location quick reply which allows people to send their location in the Messenger thread will no longer be rendered. We recommend businesses ask for zip code and address information within the thread. While we are sunsetting the existing version of Share Location, in the coming months we will be introducing new ways for people to communicate their location to businesses in more valuable ways.
• Share Button within the media, list and generic templates will no longer render. People can use the Messenger forward functionality instead of the Share Button.

Won't function with the new app

• Begin share flow Messenger extension SDK that allows developers and businesses to trigger a share experience from a webpage that loads within Messenger . As a workaround, developers can generate a link using the context in the webview and provide a way for user to copy the link and share it in the Messenger conversation.
• Share to Messenger SDK that allows people to share links and media from apps to Messenger will no longer be supported. Businesses and developers might need to make modifications to their app to trigger native OS sharing. People will be able to share content to Messenger using the native sharing features that is built into their devices.
• Messenger Codes the Messenger camera will no longer support scanning these codes. We believe this experience will be more seamless by leveraging the phone's native capabilities to scan QR codes with m.me links.

Will render differently in the new app

• Vertical list templates will no longer be supported. Instead, we recommend businesses use the horizontal scrollable carousel template. Vertical list templates will render as horizontal scrollable carousel template post August 15th.
• Nested menu will no longer be supported. To create a more seamless experience for people on Messenger, we are transitioning from nested persistent menu to a single layer menu format. We believe this will create an even better experience for people on Messenger. Nested menu items will render as a flat list.
• Open Graph template which allows people to play songs inline within Messenger will no longer be supported. As a fallback, we are rendering the generic template which links to the URL. When a user clicks on the song that is shared in Messenger, the user will be directed to the audio streaming platform's website or app.

Messenger Bot Reviews will be removed on August 15, 2019. They allowed people to leave a star rating and review for a bot. Page owners will no longer be able to view these ratings for their app and Page in the Page Settings or in App Dashboard.

May 08, 2019

Breaking Change Notice

Effective as of today, the parameter seq will always be 0 for all Messenger webhook events. This deprecation was announced on November 8, 2016. After Jul 31, 2019 the seq parameter will no longer be included in webhook events. To de-duplicate messages use the mid parameter.

April 30, 2019 - V3.3

• We are introducing a new Page control to allow a Page admin opt into a Page messaging rate limit to prevent the Page from being transitioned into a high-MPS Page.
• We are introducing a new sample Messenger App, Original Coast Clothing, to showcase Messenger automation features. This demo includes a how-to guide and open-source code to deploy on your server.

Breaking Changes

The following breaking changes apply to version 3.3+ of the Graph API, and will apply to all lower versions on July 31, 2019.

• The Broadcast API will support the Page-level subscription feature only, as the app-level pages_messaging_subscriptions permission has been deprecated.
• The Messaging Insights API will remove 2 outdated metrics: page_messages_active_threads_unique and page_messages_reported_conversations_by_report_type_unique.

The following breaking changes apply to version 3.3+ of the Graph API, and will apply to all lower versions on June 30, 2020 (Updated on December 4, 2019).

• The Conversation API and Private Reply endpoints now support pages_messaging permission as we deprecate read_page_mailboxes on April 30, 2019. For apps previously approved with read_page_mailboxes but not pages_messaging, we encourage developers to apply for the permission as soon as possible to avoid any service disruption.
• The Pages webhook field conversations is deprecated. Please migrate to use other webhook fields supported in Messenger platform instead.

January 8, 2019

Breaking Change Notice

• User Profile API: We previously updated default access for the User Profile API to only include name, first_name, last_name, and profile_pic. Effective as of today, all apps shall have access to additional profile fields if they have been approved in app review. You may apply for access to additional fields in the Messenger Platform tab of your app console.
• Customer chat plugin (beta): Starting today, you will need to use sdk/xfbml.customerchat.js library in order to render the customer chat plugin on your website. You'll no longer be able to use sdk.js to load the plugin.
• Checkbox Plugin: Following the default state of the checkbox plugin being unchecked, as of April 9, 2019, we will no longer allow a pre-checked state.

December 4, 2018

• Page-level Subscription Messaging Permission: If your app was granted the subscription messaging permission at the app-level, you should migrate to Page-level permission as soon as possible, however, as we continue to review our Subscription Messaging policies, developers provided access to send messages via app-level permissions may continue to do so until further notice.

September 27, 2018

• Persona API (Beta): This new API introduces the concept of "personas" to the Messenger Platform, which allows you to invoke different identities for your bot in-thread. When a persona is invoked, the user icon and display name for the bot is switched. The Page name continues to be shown in the header of the thread.
• Customer Chat Wordpress Plugin: The official Messenger Customer Chat plugin has been published on wordpress.com.
• Message Tags: The BUSINESS_PRODUCTIVITY message tag is now available for sending non-promotional, business-related updates outside the 24+1 standard messaging window. The restriction on which templates may be sent using message tags has also been removed. Tagged messages may now use any template, as well as text.
• Platform Release Versioning: As of this release, we will no longer be assigning version numbers to Messenger Platform releases to avoid confusion with Graph API version numbering, and to enable a more frequent release cadence.

July 26, 2018

Breaking Change Notice

• User Profile API: The following changes to the Messenger Platform's User Profile API have been announced:

  • Default profile fields: By default, the API will only return name, first_name, last_name, and profile_pic fields.
  • App-level extended profile field permissions: To access additional user profile fields, app developers must apply for each field in the Messenger Platform tab of the app console. For more information, see User Profile API - Available Profile Fields.
  • Deprecated fields: The last_ad_referral and is_payment_enabled fields are now deprecated, and will be removed from the API on October 30, 2018.

For apps created before the release of Graph API v3.1 on July 26, 2018, these changes will go into effect on January 8, 2019. Apps must be resubmitted and be approved for extended profile fields before this date.

For apps created after the release of Graph API v3.1 on July 26, 2018, these changes are in effect immediately.

June 29, 2018

• Message ID Format: The format of the message ID returned in the message_id property of responses from the Send API has been changed.

May 30, 2018

• App Submission Process: New app submissions are now required to be set to 'development' mode prior to submission.

May 23, 2018

• App Submission Process: App review for bots no longer requires developers to add test users.

May 22, 2018

• Built-in NLP: Added new sentiment entity to default NLP.

May 11, 2018 - Messenger Platform 2.4

• The Customer Chat SDK is now included in the Facebook JavaScript SDK, and enables programmatic control of customer chat plugin features, such as hiding/showing the plugin, hiding/showing the greeting dialog and more.
• The customer chat plugin now supports sender actions, user data quick replies, and enables users to send attachments.
• Broadcast API introduces advanced targeting with label predicates, and enables easier broadcast management with scheduling.
• Send to Messenger plugin now offers 20+ pre-defined strings to display as the plugin's button text.
• Handover protocol makes it easier to manage thread state with the Thread Owner API, which returns the ID of the app that currently has thread control.
• Messaging Insights API adds the page_messages_total_messaging_connections metric. This replaces the page_messages_open_conversations_unique metric, which is now deprecated.
• Send API will automatically append default values for message sends that do not include the messaging_type property. Developers should continue to implement messaging_type as soon as possible.

May 1, 2018

• Built-in NLP integration with the Page inbox lets you automatically create a Wit.ai app and bootstrap it with past conversations from your Page Inbox.
• AR Camera Effect for Messenger (closed beta) introduces the ability to add augmented reality and other camera effects to bots. These effects can be presented to the user with template buttons, quick replies, and click to Messenger ads.
• App review is once again open to all apps. In addition to the Messenger Platform's submission and review requirements, some apps will need to meet new approval requirements. For more information, read the announcement.

April 4, 2018

• Customer Matching via the Send API is now in closed beta, and is no longer accepting applications for new Pages. Pages that have previously been approved to use customer matching via the Send API and the Customer Matching API may continue to use the feature.

March 19, 2018

• Customer chat plugin (beta) now supports the greeting_dialog_display and greeting_dialog_delay attributes. The minimized attribute is now deprecated; developers should migrate to using greeting_dialog_display as soon as possible.

February 26, 2018 – Messenger Platform 2.3

• Email and phone number quick replies now enable a simple way to ask the user to provide their email or phone number. The content of the quick replies are auto-populated from the user's Facebook profile. If the person has more than one email or phone number associated with their account, a separate quick reply will be shown for each.

• Customer chat plugin (beta) introduces additional enhancements that will roll out this week, including an easy setup tool, in-browser notifications, and persistent menu support.

• Messaging Insights API is updated with two new metrics: open conversations, and new conversations.

• Page Inbox support for request thread control is now included in the handover protocol. Moving the conversation from 'Done' to 'Inbox' now automatically triggers a messaging_handovers webhook event.

• Message Tags are updated for three new use cases based on your recommendations: COMMUNITY_ALERT, CONFIRMED_EVENT_REMINDER, NON_PROMOTIONAL_SUBSCRIPTION.

• Checkbox Plugin now supports customization, including light and dark themes, a transparent background, and center alignment of the plugin content.

• Broadcast API is officially released from beta. Thanks to all the great developers that implemented and gave us feedback!

Upcoming Breaking Changes

• Page-level Subscription Messaging: Access to send subscription messages must now be applied for at the Page-level. Bots may continue to send subscription messages with the app-level permission until Dec 31, 2018, but Page admins that wish to continue sending subscription messages should apply for the new Page-level access as soon as possible. Page admins may apply for subscription messaging in the Messenger Platform tab of their Page settings.

• NON_PROMOTIONAL_SUBSCRIPTION message tag: Pages that send subscription messages, are now asked to implement NON_PROMOTIONAL_SUBSCRIPTION as a message tag, rather than a messaging type. Beginning May 7, 2018, all Pages must include this message tag to flag all messages sent under subscription messaging policy.

February 13, 2018

• Handover Protocol - Request Thread Control: Introduces the /request_thread_control endpoint that allows secondary receiver apps to request thread control from the primary receiver app.
• Message Tags: Added an additional use case for the ISSUE_RESOLUTION tag.

February 1, 2018

• Customer chat plugin (beta): Customization of the following is now supported in the Customer chat plugin: logged in greeting, logged out greeting, theme color.

December 5, 2017

• Share to Messenger: The Facebook Sharing SDK has been updated to support sharing from native iOS and Android apps directly into Messenger conversations.

November 22, 2017

• Built-in NLP: Added 8 languages and 5 new entities to the default model.
• Messenger Profile API: whitelisted_domains updated to accept a maximum of 50 domains. Previously the maximum was 10.

November 20, 2017

• Send API: The character limit for text messages has been increased from 640 to 2000.

Breaking Change Notice

Beginning February 19, 2018, the following breaking changes will go into effect for the checkbox plugin and customer matching via the Send API.

• Send API requests that use user_ref from the checkbox plugin or phone_number from customer matching to identify the message recipient will no longer trigger delivery of message_reads, message_deliveries, or message_echoes events to your webhook.

• Send API requests that use user_ref from the checkbox plugin or phone_number from customer matching to identify the message recipient, the Send API will no longer include the recipient_id property in the API response.

November 7, 2017 - v2.2

• Broadcast API is an open beta release that allows bots with the pages_messaging_subscriptions permission to send subscription messages to a multiple recipients with one API call. Messages can be sent to all open conversations or a set of PSIDs by using custom labels. You can also estimate the reach of a broadcast before it is sent and get the actual reach after the send takes place.

• Customer chat plugin (beta) is a closed beta release that lets you add a Messenger chat window to your website. New users can start a conversation with your bot, and returning users will see recent chat history. The plugin is also optimized for the mobile web.

• Media template is a new structured message template for sending images and video. The template supports sending images, videos, and animated gifs using an attachment_id, or the Facebook URL for any media that you have uploaded to Facebook, which means no more limits on the length of videos. The media template also supports adding an optional button.

• Sending sponsored messages can now be done via the Messenger Platform with a single API request to the /sponsored_message_ads endpoint. This API is a thin wrapper that accepts a reduced number of properties, then calls the existing Marketing API on your behalf. Access to the API is already available to many developers, and will roll out to 100% over the next month.

• Page-level feedback is a new addition to your Page settings, available under the 'Messenger Reviews' tab, that offers page-level aggregation of ratings and reviews. Before Platform v2.2, user feedback was only aggregated at an app-level.

• Handover protocol is officially out of beta, and includes support for passing thread control to both the current and previous version of the page inbox. Rollout of support for the previous version of the inbox is expected to be available to 100% by mid-November.

• Messaging Insights API now includes additional metrics: page_messages_blocked_conversations_unique, page_messages_reported_conversations_unique, and page_messages_reported_conversations_by_report_type_unique. These metrics replace page_messages_feedback_by_action_unique, which is now deprecated and will be removed in Graph API v2.12.

• Built-in NLP now supports 11 languages for the default model, as well as default localization of date/time entities, and additional advanced settings.

• Message tags for non-promotional use cases that require messages to be sent outside the 24-hour standard messaging window now include PAIRING_UPDATE and APPLICATION_UPDATE.

Upcoming Breaking Changes

• messaging_type property should be included in the body of the request for all message sends, as of this release. Beginning May 7, 2018 the messaging_type property will be mandatory and all messages sent without it will not be delivered. For more information, see Sending Messages - Messaging Types.

• page_messages_feedback_by_action_unique metric in the Messaging Insights API is now deprecated and will be removed in Graph API v2.12. For more information, see Analytics.

August 31, 2017

3 New Message Tags

Three new message tags are available for sending non-promotional messages outside the 24-hour standard messaging window:

• ACCOUNT UPDATE: Used to confirm updates to a user's account setting. For example, when there is a change in account settings and preferences of a user profile, notification of a password change, or membership expiration.
• PAYMENT_UPDATE: Used to provide payment updates to existing transactions. For example, it can be used to send a receipt, out-of-stock, auction ended, refund, or a status change in an existing purchase transaction.
• PERSONAL_FINANCE_UPDATE: Used to confirm a user's financial activity. For example, it can be used to send notifications on bill pay reminders, scheduled payments, receipts of payment, transfer of funds, or other transactional activities in financial services.

For complete details, see Message Tags.

July 27, 2017 v2.1

• Built-in NLP is a simple way for developers to incorporate natural language processing into their bots. Built-in NLP automatically detects meaning and information in the text of messages, before it gets passed to the bot.

• Handover protocol enables cross app collaboration within a single Messenger experience. The handover protocol enables businesses to create multiple experiences within a single bot.

• Enhancements:

  • The new SDK for payments makes the Messenger webview payment process easier and more efficient. Customers can now pay using a one-step process through Messenger webview. The webview payments SDK for Messenger Platform v1.2 - 2.0 is now deprecated - support will continue for these versions through February 1, 2018.
  • Added expanded set of Facebook Page buttons: Shop Now, Get Support, Get Updates, Play Now and Get Started.
  • Added desktop support for Messenger Extensions SDK that extends functionality across mobile and web. This allows features like user ID and sharing to be available on desktop.
  • Updated customer matching API allows matching prior to sending a message to a phone number, and optionally a name, via the API.
  • Added Chat Extensions for Global Pages. Enables thread sharing across regions using the webview and Chat Extension.
  • Added policy enforcement notifications, which send notifications when a bot has been blocked or policy issues arise.
  • Added new messaging tags to make it easier to respond to customers’ questions and provide updates: APPOINTMENT_UPDATE, GAME_EVENT, TRANSPORTATION_UPDATE, FEATURE_FUNCTIONALITY_UPDATE, TICKET_UPDATE.

April 18, 2017 – v2.0

• Discover tab added to Messenger, showcasing popular bots in our ecosystem, nearby places that people can message, and businesses that offer support or answer questions.

• Chat Extensions lets bots build interactive, social features that users can invoke directly into their conversations via the composer.

• Parametric Messenger Codes let a bot dynamically generate multiple Messenger codes that provide different functionality when they are scanned. Users can also now scan codes by holding down on the main camera interface in Messenger.

• Enhancements:

  • The ID Matching API enables the pairing of ASIDs and PSIDs between an app and a bot belonging to the same business

  • Open Graph Template lets bots send open graph content directly to threads. Currently supports only music URLs natively with inline playback.

  • Bots can now access referral information when users enter via a Messenger Ads.

  • Released the Platform Design Kit, a library of components for designing bots.

April 5, 2017

• Introduced Message Tags, allowing several use-cases for messages to be sent beyond the 24+1 limit.

March 2nd, 2017 – v1.4

• Completely re-designed Persistent Menu with several major changes:
  • Up to 3 levels of submenus
  • Ability to turn off freeform input
  • Localization support
• Several new sharing features to help your bot gain viral traction:
  • Links shared from webview now automatically contain attribution link back to your bot. Can be disabled.
  • Customized Sharing from webview via Messenger Extensions
  • Share button now allows specifying a message, rather than only sharing the bubble it was included in.
  • Bot deep-links via m.me now supported via all the above-mentioned messages.
• Added Messenger Profile API for accessing your bot's properties. Replaces the Thread Settings API. Added a way to set a target audience for your bot.
• Improved Customer Matching. Increased match rate and ability to react when the user accepts your bot's message request.
• Added Page Messaging Insights API
• Added Messenger Code API to programatically fetch the Messenger Code for a bot or page.
• Added pre-checkout webhook event for payments
• Added Attachment Upload API
• Enhancements:
  • Ability to get supported features in the webview
  • Generic templates have an image aspect ratio option.
  • Increased text limit for messages and button template from 320 to 640 characters
  • Increased limit on quick replies to 11 items

November 8, 2016 – v1.3

• Support for Ref Param in m.me links
• New Checkbox Plugin
• New List Template
• Tokenized Payments support. Payments still in BETA, request access.
• Better Testing for Payments. You don't have to be whitelisted to start testing.
• Added list of apps running a page. You can find it in to Page Settings/Messaging tab.
• Improved error reporting and clear subcodes
• Deprecation announcement: seq id field on Messenger webhooks

September 12, 2016 – v1.2

• Introduced Payments in beta! Request access through this form.
  • For native payments use new Buy Button along with Generic template
  • For payments from the web see Webviews and Extensions
• Added Webviews and Extensions to get user id for personalization, close the webview and call payments in the browser
• Added Share Button type (currently supported in Generic template only) so that people can share message bubbles
• Added Icons support to Quick Replies
• Added Location Quick Reply type
• Added webview_height_ratio parameter for Url Button to customize webview height
• Added attachments reuse support so that you don't have to upload the same attachments every time

Also:

• Messenger Destination Ads are now available under the website clicks objective - that means you can acquire users directly into your bot with no friction
• Export your bot analytics on the app level to see block rates and open threads for all your pages.
• New welcome screen when people first enter a conversation with your bot

August 30, 2016

• Added client-side events for the "Send to Messenger" plugin

August 15, 2016

• Added a new doc: Messenger Platform Policy Overview. Please review as policy changes may impact your integration.
• Re-added the Complete Guide which has now been broken up into multiple sections.
• Doc navigation changes.

July 1st, 2016

Send API

• Video, audio, gif and file sends. Support both URLs and file upload.
• Sender Actions: set read receipts and typing indicators.

Receive API

• New event: message_echoes. Allows developers to receive all messages sent by pages.
• New event: message_reads. To notify the developer/page a message was read.
• New field: app_id, to identify the source of the bot message.
• New field: metadata, passed from the Send API and sent to the message_echoes callback, to help interoperability betwen multiple bots.

User experience

• Breaking change: Get Started button. Triggers a postback received callback instead of firing a message automatically.
• New input style: Quick replies. A new way for bots to receive input with ephemeral buttons attached to the last message
• New button type: Phone number to invoke the native phone dialer
• New thread setting: Persistent menu. Supports postbacks and urls with up to five elements
• New thread setting: Greeting text. To communicate your bot's functionality to first-time users.
• Browser close. To allow automatically closing the browser window at the end of a custom web UI flow.
• Account linking and unlinking: secure protocol for businesses to retrieve a page scoped user ID from within Messenger
• Bot feedback: Users are able to leave a 5-star review and provide feedback for developers.

April 12, 2016

• Messenger Platform launched.