- In a January announcement introducing Facebook Graph API v19, Meta stated that its current Facebook Groups API is deprecated in the new Graph API version and will be removed within 90 days.
- The new API version will automatically enable the feature that allows private replies in Facebook Groups, eliminating the need to use the Groups API.
- Reactions suggest that the API shutdown would impact developers and digital markets, potentially putting companies out of business, particularly those that provide social media post schedules and automation.
Based on monthly active users, Facebook is the most popular social media platform. Monthly, Facebook has 3.05 billion and 2.09 billion daily active users, as of a 2024 report.
According to Meta, “Graph API is the primary way to get data into and out of the Facebook platform. It's an HTTP-based API that apps can use to programmatically query data, post new stories, manage ads, upload photos, and perform a wide variety of other tasks.”
Developers and companies use the Group API to plan posts to Facebook Groups. Because of the removal of Reviewable Features, publishing to groups, and member information access by groups in the new Graph API version v19, the Groups API is no longer supported.
Facebook Groups do not have any ad returns, which could be the reason for deprecating the Groups API, despite developers' claims that they do not know why Meta is bringing in new development. However, Meta has yet to state its reason.
Another concern stemming from the new development is that “Meta hasn’t clearly explained if posting on groups will be done with a Page Access token going forward; as the way the announcement is worded, it seems that part is only relevant for those posting private replies, not posting to the group as a whole,” according to a report.
After receiving a Private Replies webhook, developers must confirm using a Page Access Token when requesting the Groups Post endpoints through the Groups API, according to the Meta announcement. To manage Facebook Pages, Graph API calls require page access tokens.
Recently, Meta reportedly shut down its developers' bug portal, raising the dust that Meta is likely not prioritising developers’ interests.
