Error Codes

When a Send API request fails, you'll receive a JSON response describing the corresponding error code and message. Messenger Platform errors are grouped by code, with a different message depending on the error condition.

Below is a list of common errors that you should consider handling at run-time.

Example

{
  "error": {
    "message": "Invalid OAuth access token.",
    "type": "OAuthException",
    "code": 190,
    "error_subcode": 1234567,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Internal Errors

Code	Subcode	Message
`1200`	--	Temporary send message failure. Please try again later.

Limit Errors

Code	Subcode	Message
`4`	`2018022`	Too many send requests to phone numbers
`32`	`2018256`	Broadcast exceeds the Audience threshold. See Broadcast API limits
`100`	`2018109`	Attachment size exceeds allowable limit
`613`	--	Calls to this API have exceeded the rate limit
`613`	`2018338`	Warning! You are engaging in behavior that may be considered bothersome or abusive by users. You must significantly decrease the rate at which you are sending messages using message tags to this person. Further misuse of API features may result in messaging restrictions being placed on your Page
`100`	`2018144`	Messages to an Instant Games user have exceeded Instant Games policy.

Bad Parameter Errors

Code	Subcode	Message
`100`	--	Invalid `fbid`.
`100`	`2018001`	No matching user found
`100`	`2018014`	Cannot send both message and state at the same time.
`100`	`2018164`	Incorrect App ID.
`100`	`2018260`	The custom label id provided has an invalid format. See Targeting Broadcast
`100`	`2018261`	The Custom Label ID you have specified does not exists. See Targeting Broadcast
`100`	`2018320`	Invalid product id. See Product Template
`100`	`2018328`	Product template is not supported below version 8. Use api version 8 or higher to use product templates. See Product Template

Access Token Errors

Code	Message
`190`	Invalid OAuth access token.

Permission Errors

Permission errors can occur for multiple reasons but generally fit into two main categories:

A specific permission has not been approved.
The person has not opted-in to receiving messages from the page by using a Messenger entry point.

Code	Subcode	Message
`10`	`2018278`	This message is sent outside of allowed window. Learn more about the new policy here
`10`	`2018065`	This message is sent outside of allowed window. You need News Messaging permission to be able to do it.
`10`	`2018108`	This Person Cannot Receive Messages: This person isn't receiving messages from you right now.
`200`	`1545041`	Message Not Sent: This person isn't available right now.
`200`	`2018028`	Cannot message users who are not admins, developers or testers of the app until pages_messaging permission is reviewed and the app is live.
`200`	`2018027`	Cannot message users who are not admins, developers or testers of the app until pages_messaging_phone_number permission is reviewed and the app is live.
`200`	`2018021`	Requires phone matching access fee to be paid by this page unless the recipient user is an admin, developer, or tester of the app.
`551`	`1545041`	This person isn't available right now.

Account-Linking Errors

Code	Message
`10303`	Invalid `account_linking_token`

Thread Owner API Errors

Code	Message
`2018171`	Only available to Primary and Secondary Receivers.
`2018234`	Denying visibility of any secondary receiver to another secondary receiver other than itself.
`2018237`	The page needs to have PRIMARY RECEIVER and SECONDARY RECEIVER apps setup
`2018321`	The chat is currently controlled by Messenger while the user is in an automated question and answer flow. Please wait for the flow to finish before trying again.