I have migrated our App to the IG API with IG Login using instagram_business_basic permissions due to the Basic Display API going out on Dec 4th, 2024. This new API works for only a handful of our clients. When trying to get a long-live token for a portion of our clients' IG accounts the API call returns the following error: "Unsupported request - method type: get". The endpoint we are using to get a long-live token is: GET https://graph.instagram.com/access_token ?grant_type=ig_exchange_token &client_secret=YOUR_APP_SECRET &access_token=SHORT_LIVED_ACCESS_TOKEN
The original API call is: GET https://www.instagram.com/oauth/authorize ?client_id=APP_ID &redirect_uri=REDIRECT_URI &scope=instagram_business_basic &response_type=code
It is very unclear to me why it works for some clients but not for others

Since Meta has moved pages from in-stream ads to Content Monetization, the video_insights / total_video_ad_break_earnings has stopped showing up.

It gives this error:

{ "error": { "message": "(#200) Monetization metrics are only visible for Page admins with access to monetization insights.", "type": "OAuthException", "code": 200, "fbtrace_id": "Ap-R3KlquI-LCVIDcC9dXqD" } } 

We, and our clients, have the correct admin rights and were able to get earnings data before the update. The update is the only thing that has changed.

How do we update the code to make it work?

In our application, we currently use the Instagram Display API, but it will be deprecated on December 4, 2024. We are considering transitioning to the Instagram Business Login API. However, our application does not include any messaging-related functionality, yet the instagram_business_manage_messages permission appears to be required to publish this product.

Does anyone know whether implementing messaging functionality is mandatory for using the Instagram Business Login API, or is this a mistake? Is it possible to publish the product without the instagram_business_manage_messages scope if the application does not deal with messages?

I'm seeing inconsistent responses from the Page Blocked endpoint when attempting to block users by PSID. Specifically I'm able to block some users successfully while others return the error response:
{
"error": {
"message": "(#100) Invalid parameter",
"type": "OAuthException",
"code": 100,
"fbtrace_id": "AqgawKrSbbaHGT7HT016Gpd"
}
}
I'm using the same access token across all of the requests and I'm able to retrieve the user who cannot be blocked by PSID from the graph session without issues. This issue is blocking our customers from blocking users within the sprout app.
Including Saved Graph Sessions, the facebook page is called "Eat Bacon" and it's ID is 1656957550981542 * Session retrieving all blocked users for Eat Bacon account * https://developers.facebook.com/tools/explorer/331741700416/?session_id=540928055504801 * Session where I blocked the user Earl Scout successfully(8982583745131907) * https://developers.facebook.com/tools/explorer/331741700416/?session_id=1128228859021963 * Session where I was unable to block user Nick Cole (7843315795753926) * https://developers.facebook.com/tools/explorer/331741700416/?session_id=445119528625763 * Session retrieving user details about user Nick Cole to demonstrate user exists (7843315795753926) * https://developers.facebook.com/tools/explorer/331741700416/?session_id=888386910135648
I see that the error code 100 is mentioned in the documentation as Invalid Parameter, but this behavior seems like a bug to me. I'm using the same formatting and access token between the successful and failing API calls to the blocked endpoint with the only difference being the actual PSID value being passed in.
Link to relevant documentation: https://developers.facebook.com/docs/graph-api/reference/page/blocked/

We have a Facebook application for which we are getting the following error: "Application does not have required permission commerce_account_read_settings, commerce_manage_accounts or the capability to make this API call." We requested these permissions on August 3, 2021 and they (and others) were approved after an app review.
What can we do in this situation?