The error codes and messages listed in this article might not be up-to-date. For the most updated list of error codes, visit the Meta’s documentation here.
Here is a list of Facebook Messengers error codes, their possible causes, and suggested solutions:
| Error code | Error sub-code | Description | Possible cause and suggested solution |
| 1 | 99 | Unknown error | Advanced access, business verification or permission is required |
| 1 | 1357046 | Received invalid JSON reply | Endpoint error due to invalid JSON file. Please check the file you included in the message to try again. |
| 2 | / | An unexpected error has occurred. Please retry your request later. | An unexpected error occurred when making calls to the Meta social graph. Please check the status of the Meta Developer Platform to determine if there are issues affecting API calls. This error may also occur if a customer has blocked your business from messaging them. |
| 2 | 2018344 | Service temporarily unavailable Privacy ToS not accepted – To use the inbox label API, you need to accept the privacy ToS. Click the link to accept: https://www.facebook.com/100841475479486/inbox/page_contact_tos/ |
Service is temporarily unavailable. Page admin is required to accept the Privacy Terms of Service for Custom Labels. |
| 4 | / | Rate Limit error: Application request limit reached. Rate Limit error: Too many send requests to phone numbers |
Reached rate limit due to too many requests sent to phone numbers at the same time. Pause send requests until current ones drop below the limit. |
| 4 | 2018354 | Marketing Messages – There has to be a minimum delay between 2 notifications for the given notification | Marketing message frequency exceeds the limit set in the notification_messages_frequency field. Please keep track of which customers you have sent messages to per the agreed cadence to avoid duplicate messages sent. |
| 9 | 2018352 | User is performing too many actions | Customer has exceeded the allowed limit for Marketing Message opt-in requests |
| 10 | / | No Permission For Pages. Associated to Instant Games. | No permission to access Pages associated with Instant Games. The User Profile API is not available for PSIDs linked to Instant Game Pages. |
| 10 | 1404170 | Application does not have permission for this action | The application does not have permission for this action. Your Page is temporarily restricted from sending Marketing Message opt-in requests. |
| 10 | 1893015 | (#10) This user has currently stopped notification messages for this topic | This customer has currently paused notification messages for this topic. This may occur when your Page sends a Marketing Message after the customer clicks on "Stop these messages". |
| 10 | 2018336 | User thread impact | Unable to get a valid response as the User Thread is impacted. |
| 10 | 2534022 | This message is sent outside of the allowed window. | This message is sent outside of the allowed conversation window. Please note that you can only send a message to a customer within 24 hours of receiving the customer's message. |
| 10 | 2534077 | Cannot verify the connection between the IG account, the logged in user and the page. Please try reconnecting or verify if the user needs 2–factor authentication. | Unable to verify connection between the Instagram account, the signed in user, and the Facebook Page. Please try reconnecting the account or ensure the user has enabled 2-factor authentication. You can also try unlinking and relining the Facebook Page and the Instagram account to resolve this issue. |
| 10 | 2018278 | This message is sent outside of the allowed window. Learn more about the new policy here | This message is sent outside of the allowed conversation window. Please note that you can only send a message to a customer within 24 hours of receiving the customer's message. |
| 10 | 2018065 | This message is sent outside of the allowed window. You need News Messaging permission to be able to do it. | This message is sent outside of the allowed conversation window. Please note that you can only send a message to a customer within 24 hours of receiving the customer's message. |
| 10 | 2018108 | This person cannot receive messages: This person isn't receiving messages from you right now. | This customer cannot receive messages from you at the moment. Please try again later. |
| 100 | / |
Bad parameter error: Invalid FBID. Bad Parameter Error: No matching user found. notification_messages_token is invalid notification_messages_token has expired |
Bad parameter error. This may occur due to invalid FBID, no matching customer found, or notification_messages_token is invalid or has expired. Please ensure the ID or token you are using is valid. |
| 100 | 33 | Unsupported get request. Object with ID * does not exist, cannot be loaded due to missing permissions, or does not support this operation. | GET request is not supported. The Object with the ID does not exist, cannot be loaded due to missing permissions, or does not support this action. Please make sure the ID in your request exists and your application has the necessary permissions to access it. |
| 100 | 2018001 | No matching user found | Unable to find matching customer. Please check and try again. |
| 100 | 2018008 | Failed to fetch the file from the url. Check that the URL is valid, with a valid SSL certificate, valid file size, and that the server is responding fast enough to avoid timeouts. | Unable to fetch file from the URL. Please check if the URL is valid, with a valid SSL certificate. Please also ensure that the file is within the expected limits, and the server is responding quickly enough to avoid timeouts. |
| 100 | 2018014 | Cannot send both message and state at the same time. | You cannot send both message and state at the same time. Please check and try again. |
| 100 | 2018047 | Upload attachment failure. A common way to trigger this error is that the provided media type does not match type of file provided int the URL. | Unable to upload attachment. This may occur due to the provided media type not matching with the type of file provided in the URL. |
| 100 | 2018074 | Possible invalid ID or you do not own the attachment. | The attachment ID provided may be invalid, or you do not have ownership of the attachment. Please review the documentation for the Attachment Upload API to ensure you are providing the correct ID and have the necessary permissions. |
| 100 | 2018109 | Attachment size exceeds allowable limit | The attachment file size exceeds the allowed limit. Please check and try again. |
| 100 | 2018164 | Incorrect App ID. | Incorrect app ID. Please check and try again. |
| 100 | 2018294 | Video upload timed out or video is corrupted. Note that if the video can't be fetched within 75 seconds, it will time out. | The video upload has timed out or the video file is corrupted. Please note that if the video cannot be fetched within 75 seconds, the upload will time out. Try uploading the video again and ensure it is not corrupted. |
| 100 | 2018320 | Invalid product id | Invalid product ID. Please make sure the product ID you are using in your Product Team is valid and your app has permission to access it. |
| 100 | 2018328 | Product template is not supported below version 8. Use API version 8 or higher to use product templates. | Product Template is not supported below version 8. Please use API version 8 or above to use Product Templates. |
| 100 | 2534013 | The page is not linked to an Instagram account | This Facebook Page is not linked to an Instagram account. The Facebook page ID you use in your API calls must be linked to your Instagram Professional account. |
| 100 | 2534014 | No matching Instagram user | Unable to find matching Instagram user for this customer. Please make sure the ID you are using is a valid Instagram-scoped ID. Instagram User IDs are not supported. |
| 100 | 2534015 | Invalid message data | Invalid message data. Please make sure the type of data you are sending in your message is allowed for your message type. |
| 100 | 2534025 | The comment is invalid for a private reply | Invalid comment for a private reply. Please make sure the type of data you are sending in your private reply is allowed. |
| 100 | 2534029 | The business has been blocked from sending messages via the IG Messaging API | Unable to send message via the Instagram Messaging API. Please make sure you don't have any policy violations that must be rectified before you can send messages using the Messenger Platform. |
| 100 | 2534037 | The action is invalid since it's not the thread owner. | Unable to perform this action as you are not the owner of this conversation thread. Please ensure your app has the necessary permissions and access tokens to manage this conversation. |
| 190 | Access Token Error: Invalid OAuth access token. | Access token error. Invalid OAuth access token. | |
| 200 | Permission Error: Cannot message users who are not admins, developers or testers of the app until pages_messaging permission is reviewed and the app is live. | Unable to send messages to users who are not admins, developers or testers of the app until pages_messaging permission is reviewed and the app is live. | |
| 200 | 1545041 | Message Not Sent: This person isn't available right now. | Your message cannot be sent at the moment. The recipient is not available at the moment. |
| 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. | Phone matching access fee must be paid by this Page, unless the recipient user is an admin, developer, or tester of the app. |
| 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. | Unable to send messages to 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 | 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. | Unable to send messages to users who are not admins, developers or testers of the app until pages_messaging permission is reviewed and the app is live. |
| 200 | 2534041 | The account owner has disabled access to instagram direct messages. | Unable to access Instagram Direct Messages. This may occur due to the owner of the Instagram Professional account having revoked your app's access. |
| 551 | User Block Error: This person isn't receiving messages from you right now. | This user has blocked you, so they are unable to receive messages from you at this time. | |
| 551 | 1545041 | This person isn't available right now. | This recipient is not available at the moment. Please try again later. |
| 613 | 1893016 | Scope of service exceeded: You may not send multiple opt–in requests with the same topic to a user. | You have already sent multiple opt-in requests with the same topic to this user. Please inform the user that an opt-in request has already been sent to Messenger. |
| 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 | Your messaging behavior 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. |
| 613 | 2534040 | Calls to this api have exceeded the rate limit. | Exceeded API rate limit. Please pause API calls and try again. |
| 2022 | / | The ability to send commerce messages has been temporarily disabled. This is the result of a feature limit placed after a policy violation. | Sending commerce messages feature is temporarily disabled. This may occur due to a feature limit placed after a policy violation. |
| 10303 | / | Account Linking Error: Invalid account_linking_token. | Invalid account linking token |
| 24001 | / | User canceled payment flow | Customer has canceled the payment flow |
| 24002 | / | Payment request cannot be processed due to missing privacy url | Unable to process payment request as the privacy URL is missing. |
| 24005 | / | Failed to get user ID | Unable to get user ID for this customer. Please check and try again. |
| 36103 | / | To onboard creator accounts during Instagram phased rollout | Unable to onboard creator accounts during Instagram phased rollout. This may occur when the business is not yet eligible. Please call the Conversation API with the Page access token to check eligibility. |
| 2018144 | / | Could not send Instant Game message to the user at this time, only 5 notifications can be sent to a user within 10 days since they last played. | Unable to send Instant Game message at the moment. You can only send 5 notifications to a customer within 10 days since they last played. |
| 2018154 | / | Messenger Extensions unexpected error | An unexpected error occured in the Messenger extensions |
| 2018163 | / | Begin Share Param Validation Error | Invalid beginShare param |
| 2018166 | / | Permission not valid to call the SDK API | Invalid SDK API call permission |
| 2018171 | / | Only available to Primary and Secondary Receivers. | This action is only available to Primary and Secondary receivers. |
| 2018218 | / | No profile available for this user. | No available profile for this customer. The User Profile API does not support retrieving profile information for Messenger accounts that were created using a phone number. Please check Source Document: User Profile - Profile Info in User Profile API and try again. |
| 2018234 | / | Denying visibility of any secondary receiver to another secondary receiver other than itself. | Unable to share visibility of a secondary receiver with any other secondary receiver besides themself. |
| 2018247 | / | Insufficient permission to access user profile. | Unable to access user profile as the User Proile API has not been granted permissions to access the requested fields. |
| 2018300 | / | Message failed to send because another app is controlling this thread now. | Unable to send message because there is another app controlling this thread at the moment |
| 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. | This conversation is currently controlled by the Messenger as the customer is in an automated question and answer flow. Please wait for the flow to finish before trying again. |
| 2071010 | / | This SDK method is not supported on this Messenger client. Please upgrade | This SDK method is not supported on this Messenger client. Please upgrade and try again. |
| 2071011 | / | Messenger Extensions are not enabled – could be "messenger_extensions" was not set on a url, the domain was not added to the allow list or this is an outdated version of Messenger client | Messenger extensions are not enabled. This could be because the "messenger_extensions" was not set on a URL, the domain was not added to the allowlist, or this is an outdated Messenger client version. |
| 2071014 | / | Invalid MessageContent provided to SDK API call | Unable to perform SDK API call due to invalid message content provided |
| 2071015 | / | Invalid title string provided in message content | Invalid title string in the message content |
| 2071016 | / | Invalid subtitle string provided in message content | Invalid subtitle string in the message |
| 2071017 | / | Invalid image URL provided in message content | Invalid image URL in the message |
| 2071018 | / | Invalid item URL provided in message content | Invalid item URL in the message |
| 2071019 | / | Invalid button data provided in message content | Invalid button data in the message |
| 2071020 | / | URL data is missing in message content. Please provide item_url, button_url or both | URL is required in the message. Please input item URL, button URL, or both. |
| 2071021 | / | sharingType provided in beginShareFlow call is not valid | Invalid sharingType in the beginShareFlow call |
| 2071022 | / | Invalid attachment in begin share flow message content | Invalid attachment the beginShareFlow message content |
| 2071023 | / | Attachment type in message content must be set to template | The attachment type in your message is requred to set to template |
| 2071024 | / | Payload is not valid in message content attachment | Invalid payload attached in the message |
| 2071025 | / | Invalid open graph url provided in message content | Invalid open graph URL in the message |
| 9000001 | / | This message has been deleted by the user or the business. | This message is deleted by the customer or the business |