Connect with us

FACEBOOK

Introducing Facebook Graph API v11.0 and Marketing API v11.0

Published

on

Today, we are releasing Facebook Graph API v11.0 and Marketing API v11.0. As a part of this release, we have created this blog post to highlight broad-reaching changes that will impact parts of our developer community. These changes include announcements and product updates, reminders from prior launches, and notifications on large-scale deprecations that may affect your application(s)’ integration with our platform.

For a complete list of all changes and their details, please visit our changelog.

General Announcements and Updates

Expanding Graph API Access Levels Model to Consumer Applications

On May 6, 2021, Facebook began expanding the data access level functionality introduced in Graph API v8.0 to Consumer apps. This rollout will complete in late June / early July. This model makes testing new permissions and features easier, since anyone with a role on the app can grant it any unapproved permission or feature without having to switch to Development mode or having to use a test app.

This functionality will launch for all newly created Consumer apps in the coming weeks. Note that as part of this change, new Consumer apps must be set to Live Mode and the public_profile permission set to Advanced Access before users who do not have a role on the apps can authenticate using Facebook Login. The public_profile and email permissions are automatically approved for Advanced Access but are set to Standard Access by default.

Please refer to our access levels developer documentation to learn more about how access levels affect Consumer apps.

Advertisement
free widgets for website

Addition of Instagram ASIDs and Platform Versioning

Starting June 8, 2021, the Instagram Basic Display API will now support versioning. You may now perform versioned calls on all ‘graph.instagram.com’ endpoints using the same versioned request protocol as the Facebook Graph API.

Also, as part of this release, Instagram introduces app-scoped IDs (ASIDs), which are user IDs unique to each app and user pair.

New oEmbed Read Feature and App Review

Starting June 8, 2021, the oEmbed product has been replaced with a new oEmbed Read feature. Developers who have implemented Facebook oEmbed or Instagram oEmbed must be approved by App Review for the new oEmbed Read feature by September 7, 2021 or their oEmbed integrations will be revoked. New apps that require access may submit for review during app creation or any time after.

Audience Deletion

Changes to the Audience Deletion API

As part of Facebook’s ongoing effort to improve how advertisers create and manage their audiences, Custom Audiences (except Customer List Custom Audiences), Lookalike Audiences, or saved audiences that have not been used in active ad sets for over two years will be automatically deleted.

Advertisement
free widgets for website

For Customer List Custom Audiences, Facebook will continue to store and delete these in accordance with advertisers’ instructions. If an advertiser chooses not to use an audience tagged as an “Expiring Audience” within the allotted time frame, Facebook will treat this as an instruction to delete the audience.

Additionally, moving forward, any Custom Audience (except Customer List Custom Audiences), Lookalike Audience, or saved audience which has not been used in an active ad set for over two years will automatically be tagged as an “Expiring Audience” and will be auto-deleted 90 days after being identified as an expiring audience.

This change will be rolled out:

  • Starting June 08, 2021, for advertisers using the Marketing API (including those advertisers who use both the Marketing API and Facebook UI for ads management) and will impact all existing API versions. Auto-deletion of impacted audiences will occur on September 6, 2021 unless advertisers take action to use the flagged audiences.
  • Began May 13, 2021, for advertisers NOT using the Marketing API for ads management. Auto-deletion of impacted audiences will occur on June 27, 2021 unless advertisers take action to use the flagged audiences.
See also  Amazon rainforest plots sold via Facebook Marketplace ads

Deleted Facebook Page Based Audience Deletion

As part of our ongoing effort to improve how advertisers create and manage their audiences, we are making an update that affects Engagement Custom Audiences, associated Lookalike Audiences and saved audiences created from a deleted Facebook page. We expect impact for most advertisers to be minimal.

Starting September 08, 2021, for advertisers using the Marketing API: Engagement Custom Audiences (page, video, lead form, event, instant experience, shopping), associated Lookalike Audiences, and saved audiences that were created using a deleted Facebook page will be marked with a “warning status” with a 30 day grace period before being automatically deleted. New campaigns can continue to be created and scheduled up until this cut-off date.

Advertisement
free widgets for website

Additionally, moving forward, after September 8, 2021 advertisers will not be able to create these Engagement Custom Audiences types or Lookalike Audiences from deleted Facebook pages.

Release of Facebook Platform SDKs v11.0

Starting June 08, 2021, Facebook is releasing Platform SDKs v11.0. With this release, we are deprecating v9.0 and introducing several feature updates. Please visit the iOS SDK Changelog, Android SDK Changelog and Unity SDK Changelog to learn about important upcoming changes to these SDKs. Additionally, Facebook has posted a separate blog highlighting these updates.

Endpoint Specific Announcements and Updates

Specifying Permissible Use Cases for user_likes and user_posts

Starting June 8, 2021, in an effort to reduce risk on our platform, we are further specifying the permissible use cases for both user_likes and user_posts. If your app currently has access to user_likes and/or user_posts, and your use case is not aligned with the updated permissible use case(s), you will have until September 6, 2021 to make any necessary changes on your app, to account for it no longer being eligible to access one or more of these permissions. Beginning September 6, 2021, apps with access to these permissions that don’t fall under the new permissible use cases will be subject to enforcement action.

If you’re unsure whether your use case aligns with these updates, please proactively submit for App Review before September 6, 2021. Apps’ whose use case does align with the updated permissible use case(s) will not be impacted by this change.

Product Group and Catalog Endpoint Modifications

Starting June 8, 2021, for API v11.0+, Facebook is implementing several changes to how you engage with product group and catalog:

Advertisement
free widgets for website
  • Default Product Group Deletion will no longer allow deletion of non-empty product groups by default. Non-empty product groups can be deleted by applying deletion_method=delete_items to the deletion request. This will delete both the product group and its items.
  • Change to Default Catalog Deletion will not support the deletion of a product catalog by default if it has live product sets. A live product set is classified as being actively used (e.g., ads campaigns, promotions, and published Shops).
  • Addition of Catalog Diagnostics Endpoint utilized to retrieve diagnostics data for a given product catalog. This endpoint could help identify issues like products not showing in channels or displaying opportunities that could improve product discoverability.

Change to Inventory Field

Starting on June 8, 2021, for API v11.0+, to eliminate inconsistencies between surfaces and remove confusion around availability and inventory, Facebook will add the quantity_to_sell_on_facebook field as a replacement for the inventory field.

See also  Facebook yangiza abana ikanaca intege demokarasi: uwahoze ari umukozi wayo - BBC

The quantity displayed by this new field will not be reduced by reserved inventory, defined as inventory temporarily reserved when buyers add an item to their cart. We will continue to support the ‘inventory’ field for the near term. However, we recommend that you use the new ‘quantity_to_sell_on_facebook’ field instead.

Reminder No Action Required

New Pages Experience

On October 2, 2020, Facebook announced the new Page experience as a way for public figures, businesses and others who want to build and connect with an audience to manage their professional presence on Facebook. All classic Pages are currently being transitioned over to the new Pages experience in a gradual rollout. We are planning to complete the rollout within the next few months, and classic Pages will eventually be deprecated.

Please see the developer documents to learn how to determine whether a Page has been transitioned yet and visit the Help Center for questions.

Platform Live Status Feature Update

On June 1, 2021, Facebook launched a new Platform Live Status page to increase transparency and proactive communication with external developers using Facebook platform products. This new Facebook for Business Status page will serve as the single location for checking server health for platform and business products offered by Facebook, including Ads, WhatsApp Business API, Facebook Developer Platform, and more.

Deprecations

Facebook Analytics Deprecation

Originally announced March 30, 2021, Facebook is in the process of deprecating Facebook Analytics (FBA). After June 30, 2021, the Facebook Analytics tool will no longer be available. Additionally, we are deprecating the Dashboard Plugin for Marketing API.

Advertisement
free widgets for website

While the individual Facebook Analytics tool is going away, these alternatives are still available:

  • Events Manager
  • Ads Manager
  • Page Insights
  • Instagram Insights
  • Facebook Business Suite Insights

Messenger Platform – Airline Templates Deprecation

Starting June 8, 2021, Graph API v11.0+ will no longer support businesses’ abilities to send Airline Templates. Deprecation for the prior Graph API versions (v10.0 and below) will occur 6 months after the announcement of this change on December 6th, 2021.

We recommend businesses send boarding passes and check-in templates as images, consistent with how companies typically send these notifications in other channels.

Native Offers Endpoint Deprecation

Starting June 8, 2021, if you are using Offer Ads API, you are encouraged to use Facebook Ads instead, for building your promotions and discounts. Offer Ads API endpoints will be deprecated upon the release of Graph and Marketing API v12.0 in the fall. Though we are not officially deprecating the endpoint on the launch of v11.0, we will begin transitioning support that may cause a sub-optimal experience if you continue to use this endpoint.

Page Public Content Access – Comments Node Deprecation

Starting June 8, 2021, for Graph API v11.0+, the “id” field for all comments returned in requests using the Page Public Content Access feature will be removed. Note: nested requests will still be supported for these objects.

This change will apply to all other active API versions (v10.0 and below) on September 6, 2021.

Advertisement
free widgets for website

Page Public Content Access – Comments Node Deprecation

Starting June 8, 2021, access to the following endpoints is temporarily limited to apps that have queried them within the last 30 days:

  • gr:post:Business/client_adaccounts
  • gr:post:AdAccount/agencies
  • gr:post:BusinessRequest

API Version Deprecations:

As part of Facebook’s Graph API and Marketing API, please note the upcoming deprecations:

  • August 3, 2021: Graph API v3.3 will be deprecated and removed from the platform
  • August 25, 2021 Marketing API v9.0 will be deprecated and removed from the platform
  • October 4, 2021: Marketing API v10.0 will be deprecated and removed from the platform
  • November 2, 2021: Graph API v4.0 will be deprecated and removed from the platform
  • February 3, 2022: Graph API v5.0 will be deprecated and removed from the platform
See also  News Brief: Booster Shots, US Capitol Security, Facebook Files - NPR

To avoid disruption to your business, we recommend migrating all calls to the latest API version that launched today.

Action Item Calendar

General Announcements and Updates

  • May 12, 2021: Changes to Audience Reaping UI (Advertisers NOT using Marketing API)
  • Rolling:
    • Expanding Graph API Access Levels to Consumer Applications with planned completion in late June / early July
  • June 8, 2021:
    • Addition of Instagram ASIDs and Platform Versioning
    • Addition of oEmbed Reviewable Feature in App Review
    • Changes to the Audience Reaping API
    • Release of Facebook Platform SDKs v11.0
  • November 2, 2021: Data Deletion Requests Deadline

Endpoint Specific Announcements and Updates

  • June 8, 2021:
    • Further specification on Permissible Use Cases for user_likes and user_posts
    • Launch of Product Group and Catalog Endpoint Modifications
      • Default Product Group Deletion will no longer allow deletion of non-empty product groups by default
      • Change to Default Catalog Deletion will not support the deletion of a product catalog by default if it has live product sets
      • Addition of Catalog Diagnostics Endpoint utilized to retrieve diagnostics data for a given catalog
    • Replacement of ‘Inventory Field’ with ‘quantity_to_sell_on_facebook’ field for API v11.0+
  • November 10, 2022: Data Deletion Requests Deadline

Reminders, No Action Required

  • Rolling:
    • Began October 2, 2020: New Pages Experience announced as a way for public figures, businesses and others who want to build and connect with an audience to manage their professional presence on Facebook.
  • June 1, 2021: Launch of Platform Live Status Feature Update

General Deprecations

  • June 8, 2021:
    • Facebook Platform SDKs v11.0 will be deprecated and removed from the platform
    • Messenger Platform – Airline Templates will be deprecated and removed from the platform for v11.0+
    • Page Public Content Access – Comments Node will be deprecated and removed from the platform for v11.0+
    • Temporary Business Endpoint Restrictions go into effect
  • June 30, 2021: Facebook Analytics will be deprecated and removed from the platform
  • September 6, 2021: Page Public Content Access – Comments Node will be deprecated and removed from the platform for v10.0 and below
  • June 8, 2021: Native Offers Endpoint Deprecation
  • Fall 2021: Native Offers Endpoint Deprecation
  • December 6, 2021: Messenger Platform – Airline Templates will be deprecated and removed from the platform for v10.0 and below

Marketing API Version Deprecations:

As part of our Marketing API versioning schedule, please note the upcoming Marketing API version deprecations:

  • August 25, 2021: Marketing API v9.0 will be deprecated and removed from the platform
  • October 4, 2021: Marketing API v10.0 will be deprecated and removed from the platform

To avoid disruption to your business, we recommend migrating all calls to the latest Marketing API version that launched today. (Visit the changelog for more details).

Graph API Version Deprecations:

As part of our Graph API versioning schedule , please note the upcoming Graph API version deprecations listed below:

  • August 3, 2021: Graph API v3.3 will be deprecated and removed from the platform
  • November 2, 2021: Graph API v4.0 will be deprecated and removed from the platform
  • February 3, 2022: Graph API v5.0 will be deprecated and removed from the platform

Facebook Developers

Continue Reading
Advertisement free widgets for website

FACEBOOK

Now people can share directly to Instagram Reels from some of their favorite apps

Published

on

By

now-people-can-share-directly-to-instagram-reels-from-some-of-their-favorite-apps

More people are creating, sharing and watching Reels than ever before. We’ve seen the creator community dive deeply into video content – and use it to connect with their communities. We’re running a limited alpha test that lets creators share video content directly from select integrated apps to Instagram Reels. Now, creators won’t be interrupted in their workflow, making it easier for them share share and express themselves on Reels.

“With the shift to video happening across almost all online platforms, our innovative tools and services empower creativity and fuel the creator economy and we are proud to be able to offer a powerful editing tool like Videoleap that allows seamless content creation, while partnering with companies like Meta to make sharing content that much easier.”- Zeev Farbman, CEO and co-founder of Lightricks.

Starting this month, creators can share short videos directly to Instagram Reels from some of their favorite apps, including Videoleap, Reface, Smule, VivaVideo, SNOW, B612, VITA and Zoomerang, with more coming soon. These apps and others also allow direct sharing to Facebook , which is available for any business with a registered Facebook App to use.

We hope to expand this test to more partners in 2023. If you’re interested in being a part of that beta program, please fill out this form and we will keep track of your submission. We do not currently have information to share about general availability of this integration.

Learn more here about sharing Stories and Reels to Facebook and Instagram and start building today.

Advertisement
free widgets for website

FAQs

Q. What is the difference between the Instagram Content Publishing API and Instagram Sharing to Reels?

See also  Google, Facebook, Microsoft top EU lobbying spending - study | Reuters

A: Sharing to Reels is different from the Instagram Content Publishing API, which allows Instagram Business accounts to schedule and publish posts to Instagram from third-party platforms. Sharing to Reels is specifically for mobile apps to display a ‘Share to Reels’ widget. The target audience for the Share to Reels widget is consumers, whereas the Content Publishing API is targeted towards businesses, including third-party publishing platforms such as Hootsuite and Sprout Social that consolidate sharing to social media platforms within their third-party app.

Q: Why is Instagram partnering with other apps?

A: Creators already use a variety of apps to create and edit videos before uploading them to Instagram Reels – now we’re making that experience faster and easier. We are currently doing a small test of an integration with mobile apps that creators know and love, with more coming soon.

Q: How can I share my video from another app to Reels on Instagram?

Advertisement
free widgets for website

A: How it works (Make sure to update the mobile app you’re using to see the new Share to Reels option):

  • Create and edit your video in one of our partner apps
  • Once your video is ready, tap share and then tap the Instagram Reels icon
  • You will enter the Instagram Camera, where you can customize your reel with audio, effects, Voiceover and stickers. Record any additional clips or swipe up to add an additional clip from your camera roll.
  • Tap ‘Next’ to add a caption, hashtag, location, tag others or use the paid partnerships label.
  • Tap ‘Share’. Your reel will be visible where you share reels today, depending on your privacy settings.
See also  Why Facebook Reported the Most Impressive Earnings of 2021 So Far

Q: How were partners selected?

A. We are currently working with a small group of developers that focus on video creation and editing as early partners. We’ll continue to expand to apps with other types of creation experiences.

Q: When will other developers be able to access Sharing to Reels on Instagram?

A: We do not currently have a date for general availability, but are planning to expand further in 2023.

Q: Can you share to Facebook Reels from other apps?

Advertisement
free widgets for website

A: Yes, Facebook offers the ability for developers to integrate with Sharing to Reels. For more information on third-party sharing opportunities, check out our entire suite of sharing offerings .

First seen at developers.facebook.com

Continue Reading

FACEBOOK

What to know about Presto SQL query engine and PrestoCon

Published

on

By

what-to-know-about-presto-sql-query-engine-and-prestocon

The open source Presto SQL query engine is used by a diverse set of companies to navigate increasingly large data workflows. These companies are using Presto in support of e-commerce, cloud, security and other areas. Not only do many companies use Presto, but individuals from those companies are also active contributors to the Presto open source community.

In support of that community, Presto holds meetups around the world and has an annual conference, PrestoCon, where experts and contributors gather to exchange knowledge. This year’s PrestoCon, hosted by the Linux Foundation, takes place December 7-8 in Mountain View, CA. This blog post will explore some foundational elements of Presto and what to expect at this year’s PrestoCon.

What is Presto?

Presto is a distributed SQL query engine for data platform teams. Presto users can perform interactive queries on data where it lives using ANSI SQL across federated and diverse sources. Query engines allow data scientists and analysts to focus on building dashboards and utilizing BI tools so that data engineers can focus on storage and management, all while communicating through a unified connection layer.

In short, the scientist does not have to consider how or where data is stored, and the engineer does not have to optimize for every use case for the data sources they manage. You can learn more about Presto in a recent ELI5 video below.

Caption: Watch the video by clicking on the image above.

Advertisement
free widgets for website

Presto was developed to solve the problem of petabyte-scale, multi-source data queries taking hours or days to return. These resources and time constraints make real-time analysis impossible. Presto can return results from those same queries in less than a second in most cases, allowing for interactive data exploration.

See also  APD Chief Medina address community's concerns during Facebook Live

Not only is it highly scalable, but it’s also extensible, allowing you to build your own connector for any data source Presto does not already support. At a low level, Presto also supports a wide range of file types for query processing. Presto was open sourced by Meta and later donated to the Linux Foundation in September of 2019.

Here are some Presto resources for those who are new to the community:

What is PrestoCon?

PrestoCon is held annually in the Bay Area and hosted by the Linux Foundation. This year, the event takes place December 7-8 at the Computer History Museum. You can register here. Each year at PrestoCon, you can hear about the latest major evolutions of the platform, how different organizations use Presto and what plans the Technical Steering Committee has for Presto in the coming year.

Presto’s scalability is especially apparent as every year we hear from small startups, as well as industry leaders like Meta and Uber, who are using the Presto platform for different use cases, whether those are small or large. If you’re looking to contribute to open source, PrestoCon is a great opportunity for networking as well as hearing the vision that the Technical Steering Committee has for the project in the coming year.

Advertisement
free widgets for website

Explore what’s happening at PrestoCon 2022:

Where is Presto used?

Since its release in November of 2013, Presto has been used as an integral part of big data pipelines within Meta and other massive-scale companies, including Uber and Twitter.

The most common use case is connecting business intelligence tools to vast data sets within an organization. This enables crucial questions to be answered faster and data-driven decision-making can be more efficient.

How does Presto work?

First, a coordinator takes your statement and parses it into a query. The internal planner generates an optimized plan as a series of stages, which are further separated into tasks. Tasks are then assigned to workers to process in parallel.

Workers then use the relevant connector to pull data from the source.

Advertisement
free widgets for website

The output of each task is returned by the workers, until the stage is complete. The stage’s output is returned by the final worker towards the next stage, where another series of tasks must be executed.

The results of stages are combined, eventually returning the final result of the original statement to the coordinator, which then returns to the client.

How do I get involved?

To start using Presto, go to prestodb.io and click Get Started.

We would love for you to join the Presto Slack channel if you have any questions or need help. Visit the community page on the Presto website to see all the ways you can get involved and find other users and developers interested in Presto.

If you would like to contribute, go to the GitHub repository and read over the Contributors’ Guide.

Advertisement
free widgets for website

Where can I learn more?

To learn more about Presto, check out its website for installation guides, user guides, conference talks and samples.

Make sure you check out previous Presto talks, and attend the annual PrestoCon event if you are able to do so.

To learn more about Meta Open Source, visit our open source site, subscribe to our YouTube channel, or follow us on Twitter, Facebook and LinkedIn.

First seen at developers.facebook.com

Advertisement
free widgets for website
Continue Reading

FACEBOOK

How to Interpret Webhook Components in the WhatsApp Business Platform

Published

on

By

how-to-interpret-webhook-components-in-the-whatsapp-business-platform

The ways customers want to connect are changing. The WhatsApp Business Platform gives businesses an integrated way to communicate with customers right where they are. In order to integrate properly when using the Cloud API, hosted by Meta, you’ll need to leverage webhooks so applications have a way to respond to events. Webhooks allow your application to monitor three primary events on WhatsApp so you can react with different functionality depending on your goals.

This article looks at these three components, goes through the information they carry, and provides some use-case scenarios to give you an idea of the possibilities.

Interpreting Different Webhook Components

To send and receive messages on WhatsApp, it’s critical to keep track of statuses and errors to help ensure you’re communicating effectively with your customers, which you can do with webhooks.

With webhooks, the WhatsApp Business Platform monitors events and sends notifications when one occurs. These events are one of three components: messages, statuses, and errors.

Let’s explore each of these and examine examples of how you can use them.

Advertisement
free widgets for website

Messages

The messages component is the largest of the three event types and contains two core objects:

  • Contacts — which contain information about the message’s sender.

  • Messages — which provide information about a message’s type and contents.

These two event types allow your application to manage and respond to people that interact with your application. The contacts object contains two pieces of information: name and WhatsApp Id. The contact’s name allows your application to use their name without further lookups. In contrast, the contact’s WhatsApp ID lets you keep track of these contacts or use the contacts/ endpoint to add additional functionality.

For instance, you can verify the customer and start the opt-in process within the customer-initiated conversation, which allows you to message them outside the initial 24-hour response window. It’s important to note that only the text, contacts, and location message types provide contact information.

The message object is where the bulk of the information is stored, including the message contents, type of message, and other relevant information. Depending on the message type, the actual payload of the message component can vary widely. It’s crucial to determine the message type to understand the potential payload. Message types include:

  • Text: a standard text-only message

  • Contact: contains a user’s full contact details

  • Location: address, latitude, and longitude

  • Unknown: unsupported messages from users, which usually contain errors.

  • Ephemeral: disappearing messages

  • Media message types: contain information for the specified media file. These types include:

    • Document

    • Image

    • Audio

    • Video

    • Voice

These different data types can have very different uses, from reviewing images and screenshots from concerned customers to collecting information about where to ship goods and send services. To use these different data types most effectively, you can create applications to handle different forms of communication, with functionalities such as:

Advertisement
free widgets for website
  • Ask your customers to provide a shipping or mailing address. You can use the location-based message feature to capture your users’ location to determine where to send their goods and services.

  • Show customers products and communicate product details through a message. You can use the referred_product field within messages to offer your users specific product details. Using this field develops a more personal, conversational shopping experience and customer interactions.

  • Build support functionality that allows customers to take and send images and videos of product concerns, and submit those for a support case. Once the user has submitted a support ticket, the app can track the case — including steps taken towards resolution and conversations between support teams and the customer through WhatsApp — using a unique case identifier.

These are just some potential features you can build using the interactivity provided by webhooks and the message object. These features extend your current communication channels and provide additional options for customers.

Statuses

Where the messages component provides your application with insight into events that originate directly from your customers, the statuses component keeps track of the results of messages you send and the conversation history. There are six status components:

  • Sent: the application sent your message and is in transit.
  • Delivered: the user’s device successfully received the message.
  • Read: the user has read your message.
  • Deleted: a user deleted a message that you sent.
  • Warning: a message sent by your application contains an item that isn’t available or doesn’t exist.
  • Failed: a message sent by your application failed to arrive.

Status components also contain information on the recipient ID, the conversation, and the pricing related to the current conversation. Conversations on WhatsApp are a grouping of messages within a 24-hour window that are either user-initiated or business-initiated. Keeping track of these conversations is vital, as a new conversation occurs when you send additional responses after the 24-hour period ends.

Some functionality you may want to add to your application based on status events includes:

  • Ensuring your application has sent generated messages, they arrived, and the recipient potentially read them by using a combination of these status types and timestamps within the status object. This information allows your application to follow up with customers if they didn’t engage.
  • Keep analytical information about your application’s messages, especially regarding business-initiated conversations. For example, if your application uses a WhatsApp customer contact list to send offer messages, the status component helps you understand how many were sent, delivered, read, responded to, or failed to measure your campaign’s success.

Errors

Finally, the errors component allows your application to receive any out-of-band errors within WhatsApp that affect your platform. These errors don’t stop your application from compiling or working but are typically caused when your application is misusing specific functionality. The following are some typical errors.

Error Code 368, Temporarily Blocked for Policy Violations

If your application violates WhatsApp Business Messaging or Commerce policy, your account may be temporarily banned. You can monitor this and pause your application while troubleshooting.

Error 506, Duplicate Post

If your workflows unintentionally generate duplicate messages, you can monitor this to find the source.

Advertisement
free widgets for website

Error 131043, Message Expired

Sometimes, messages are not sent during their time to live (TTL) duration. Use this code to know which messages to schedule for resending if needed.

Error handling is a broad, complex subject, and there are many other use cases for which you should be implementing error handling. The errors component helps extend your error handling on the WhatsApp Business Platform for greater consistency.

Conclusion

This article took a high-level look at messages, statuses, and errors returned by webhooks and explored ways you can use these three components to expand your application’s functionality.

Messages provide information on customer interactions, statuses give insight into messages your app sends, and error notices enable you to increase your application’s resilience. Webhooks are critical to ensuring your app interacts with customers seamlessly.

The WhatsApp Business Platform’s webhooks provide your applications with real-time data, enabling you to build better experiences as you interact with customers. Ready to know more? Dive deeper into everything the WhatsApp Business Platform has to offer.

Advertisement
free widgets for website

First seen at developers.facebook.com

See also  Messenger Platform Update: December 2018 + F8 Save the date
Continue Reading

Trending