Meta WhatsApp Error Code 10 (WABA Permission Denied) — API Permission Revoked / Number Not Allowlisted — Fix

Overview

Error code #10 — "Permission Denied". Appears when a required permission for your WhatsApp Business Account has not been granted or was removed. This is a Meta-side permissions problem, not a ChatDaddy bug. The request is blocked until the permission is restored.

Why This Happens

• The phone number is not allowlisted for the API action being attempted.
• API permissions were revoked or removed from the token or the connected app.
• The System User or app lost access to the WhatsApp Business Account asset.

How to Fix

1. Open Meta's Access Token Debugger: https://developers.facebook.com/tools/debug/accesstoken
2. Paste your token and click Debug to review the granted Scopes and the connected assets.
3. Confirm whatsapp_business_management and whatsapp_business_messaging are present.
4. In Meta Business Manager → Business Settings, check that the System User still has access to your WhatsApp Account asset (Business Settings → Accounts → WhatsApp Accounts → Assigned Partners/People).
5. If access or scopes are missing, re-assign the asset and generate a new token with both permissions.
6. Update the new token in your ChatDaddy WABA connection.
7. Retry the action — it should now be permitted.

Suggested Reply

The error you're seeing is Meta error code 10 — "Permission Denied". It means a required permission for your WhatsApp Business Account was not granted or has been removed. This is a Meta-side setting, not a ChatDaddy issue. 🙂

Here's how to fix it:

1. Open Meta's Access Token Debugger: https://developers.facebook.com/tools/debug/accesstoken
2. Paste your token, click Debug, and review the Scopes and connected assets
3. Confirm whatsapp_business_management and whatsapp_business_messaging are present
4. In Meta Business Manager → Business Settings, check that your System User still has access to the WhatsApp Account asset
5. If access or scopes are missing, re-assign the asset and generate a new token with both permissions
6. Update the new token in your WABA connection

Once the permission is restored, the action will work again. Let me know if you'd like me to walk you through any step! 😊