I have a question about Instagram's sending API.
The official meta documentation states the following about the per-second limit:
100 calls per second per Instagram professional account for messages that contain text, links, reactions, and stamps
10 calls per second per Instagram professional account for messages that contain audio or video content
Reference: https://developers.facebook.com/docs/messenger-platform/overview#instagram-------
I'm having trouble figuring out which limit applies to messages that contain images based on this explanation.
Does content that contains images fall under the "10 calls per second" limit? Or does it fall under the "100 calls per second" limit?
Thank you in advance for your support!

I am trying to fetch instagram dm messages through graph api, according to the documentation the endpoint contains the platform field but in graph api the field is not visible and i also tried it using postman it returned empty response {'data': []}, i have all the necessary permissions verified but it is still giving me empty response

Whether my app is in live mode or test mode, when I send a test webhook, I get the notification "The sample update was successfully sent to your server". However, no request is logged by my server at all. Also, other test webhooks do work, so my server and meta app are correctly set up. I also tried sending a message to my page from my own facebook account which is the same as this account and is the owner of the app. No event is received.
Did I understand correctly that I should be able to send and receive page messages with standard access without app approval?
Would greatly appreciate any help, thanks!

When requesting to send a message, I receive the following error from the Facebook API:
"error":{
"message":"(#10) Messaging permission check failure",
"type":"OAuthException",
"code":10,
"error_subcode":2018334,
"fbtrace_id":"As9GS3VHIhw8WRwSuv48RSl"
}
It happend in many case of several pages, Page AssetID (1618898775025382) is valid, and my Facebook profile is alive.
Feel free to make any requests to investigate the issue

Our website displays multiple payment bank options, each linked to a corresponding native mobile application using deep links (e.g., app://q?qPay_QRcode=...). The functionality was working seamlessly across all browsers, including Safari, Chrome, and in-app browsers like Messenger’s, up until August 2024.
Deep links to native banking apps still work flawlessly in Safari and Chrome. However, in the Messenger in-app browser, clicking on a deep link to open a native banking app does not trigger the native app as expected. Instead, the user is redirected to the app store, even if the application is already installed on their device. Notably, the Messenger-specific fb:// deep links continue to function properly in the same environment, indicating that the issue is isolated to third-party app deep links (such as banking apps).
This issue disrupts the payment flow for users who access our website from Messenger, leading to confusion and inconvenience. Users are unable to seamlessly transition from our web interface to their native banking apps, negatively impacting their overall experience. As the issue persists only in the Messenger in-app browser and does not affect other browsers, we believe this to be a change or restriction introduced specifically within Messenger's handling of external deep links.