WhatsApp error 131005: Access denied
Last verified against Meta for Developers - Cloud API error codes
Permission is either not granted or has been removed.What error 131005 means
Code 131005 is WhatsApp's own access-denied error, carrying the same wording as Graph API codes 10 and 200 but emitted by the messaging layer. It means your token authenticated, the request reached the WhatsApp service, and that service decided the caller is not permitted to act on this phone number or WABA. The typical trigger is a token whose System User lacks the right role on the asset, or an app that has not been properly subscribed to the WABA.
The difference from 10 and 200 is mostly which layer rejected you; the remedy overlaps heavily. One thing to check specifically for 131005 is the relationship between the app and the WABA: the app must be subscribed to the WABA (POST /{waba-id}/subscribed_apps) for messaging to work, and a missing subscription can surface as access denied on sends.
Your token is not expired, and the phone number exists; the platform just does not believe you are allowed to use it.
Why it happens
- The System User behind the token has no assignment on the WhatsApp Business Account.
- The app is not subscribed to the WABA, so message operations are refused.
- The token carries whatsapp_business_management but not whatsapp_business_messaging.
- A partner-managed WABA where the client revoked the partner's access.
- The request targets a phone number ID that belongs to a WABA the token cannot see.
How to fix WhatsApp error 131005
- 1Call GET /{waba-id}/subscribed_apps and confirm your app ID is listed; subscribe it if not.
- 2In Business Settings, confirm the System User has the WABA under Assigned Assets with full control.
- 3Inspect the token's scopes in the Access Token Debugger and regenerate with both WhatsApp permissions if either is missing.
- 4Verify the phone number ID belongs to a WABA your business can access by listing /{waba-id}/phone_numbers.
- 5Retry the send with the regenerated token after the subscription and assignment are in place.
How to stop it recurring
Make WABA subscription part of your onboarding automation and verify it in a health check rather than assuming it was done once. Keep token scopes and asset assignments in a checklist and audit them after any change in Business Manager. For partner setups, use Embedded Signup so access grants are created consistently and are visible to both parties. If the app subscription checks out, work through the authorization family in order - 190, 10, 200-299 - as laid out in the error-code guide.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
Error 131005 - quick answers
What does WhatsApp error 131005 mean?
Code 131005 is WhatsApp's own access-denied error, carrying the same wording as Graph API codes 10 and 200 but emitted by the messaging layer. It means your token authenticated, the request reached the WhatsApp service, and that service decided the caller is not permitted to act on this phone number or WABA.
How do I fix WhatsApp error 131005?
1. Call GET /{waba-id}/subscribed_apps and confirm your app ID is listed; subscribe it if not. 2. In Business Settings, confirm the System User has the WABA under Assigned Assets with full control. 3. Inspect the token's scopes in the Access Token Debugger and regenerate with both WhatsApp permissions if either is missing. 4. Verify the phone number ID belongs to a WABA your business can access by listing /{waba-id}/phone_numbers. 5. Retry the send with the regenerated…
Stop debugging WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.