WhatsApp error 131005
Error 131005: Permission not granted
Error 131005 means the access token behind the request does not have the permission that action needs, or the permission was taken away. It is a set-up problem, not a problem with the message, so a resend fails the same way until the permission is back.
Last updated
- Meta’s description
- “Permission is either not granted or has been removed.” Meta’s error codes, 5 October 2026 (opens in a new tab)
- Charged by Meta?
- No. Meta charges only for delivered messages, and this one was not delivered.
Common causes
- The app or token was never given the WhatsApp permission the endpoint needs.
- Access to the WhatsApp Business Account was removed from the app or the system user.
How to fix it
- Check the token in Meta’s access token debugger and confirm it has the permissions the endpoint needs (for sending, whatsapp_business_messaging).
- If access was removed, grant it again in Meta’s business settings, or reconnect the account.
What Fliok does about it
- Fliok treats 131005 as a definite rejection and does not retry it.
- If it shows on your sends, reconnect WhatsApp in Settings so Fliok holds a fresh token with the right permissions.
Meta sets and changes these codes. If anything here disagrees with Meta’s current reference (opens in a new tab), Meta is right.
Is 131005 the same as an expired token?
No. An expired token has its own code (190). 131005 means the token works but is missing a permission.
Related codes
Other errors you may see
Let Fliok catch it before Meta does
Blank variables, missing header files and closed windows are checked before a message leaves. Start on the Free plan.
Free forever plan · Keep your WhatsApp app