Skip to main content

Accept DM Request endpoint

Hi, we are experiencing a major bottleneck when responding to some of our messages in Instagram, the reason being that we can respond to persons that sends us messages if they land into our inbox but we can't respond to messages that land in "message requests" because there is no way of accepting or rejecting a request message API endpoint. could you please add such an endpoint or integrate auto acceptance or rejection on the send message api endpoint?

Status: Completed3 comments

Log in to comment and vote

Comments3

  • Miquel Palet López

    Team•

    Oct 6

    Shipped: GET /v1/inbox/conversations?folder=requests lists Facebook and Instagram Message Requests live from Meta (first page, each item marked folder: requests), and POST /v1/inbox/conversations/{conversationId}/accept with { "accountId": "...", "message": "..." } accepts one by replying (Meta has no separate accept call). When Meta won't list the folder for an account you get a 400 PLATFORM_LIMITATION. Docs: "Inbox".

  • Miquel Palet López

    Team•

    Aug 26

    There is no accept or decline endpoint, and there never has been: Meta does not expose the Requests folder at all, its docs say plainly that "inbox folders are not supported" and webhook payloads carry no folder information. The good news is that you do not need to accept first. Meta's Instagram messaging docs state that a conversation from a non-follower starts in Requests and "only after your app user to respond to a message, using your app, is the conversation moved to the General folder", so your reply through POST /v1/inbox/conversations/{conversationId}/messages is the acceptance.

    Two constraints to plan around: the standard 24 hour window from the customer's last message applies (past that, send with messagingType: MESSAGE_TAG and messageTag: HUMAN_AGENT, which Instagram allows up to 7 days), and Meta stops returning request messages that have been inactive for 30 days. If sends into those threads are actually failing for you, reply here with the conversation id and the error we return and we will look at the specific case.

  • Arthur 812

    •

    Aug 23

    yes it would be really nice!