Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 3: API method

Error code 3 means the app made a call it isn't set up to make. Either the app doesn't have the capability the endpoint requires, or the token behind the call lacks a permission.

3
Code
API method
Meta's name
Authorisation
Type
On the API response
Where you see it
After fixing the cause
Retry

Quick answer

The app is missing a capability or permission for this endpoint. Check what the token has been granted, request the missing WhatsApp permission, and call again.

What WhatsApp error 3 means

Meta documents code 3 as a capability or permissions issue, and advises using the access token debugger to verify that the app has been granted the permissions the endpoint requires.

Why error 3 happens

Authorisation errors come from the token or the app's permissions. Usually one of these:

  • The token only has whatsapp_business_messaging when the call needs whatsapp_business_management, or the other way round.
  • The app hasn't been approved for the permission in Meta's app review.
  • A token was created before a permission was added to the app, so it doesn't carry it.
  • The call targets a feature that needs a separate capability on the app.

How to fix error 3

Work through these in order; the first one that turns up a problem is usually the fix.

  • Inspect the token with the access token debugger and list its granted permissions.
  • Compare them with the permissions the endpoint's reference requires.
  • Add any missing permission to the app, complete app review if it needs it, and generate a new token.
  • Retest the exact call that failed.

Should you retry after 3?

The same call keeps failing until the permission is in place. Retry with a new token once it is.

How error 3 shows up in InfiQ

If Meta rejects the send straight away, InfiQ's API answers with an HTTP error that carries Meta's own error object: error.code 3, a message beginning "(#3)" and Meta's explanation in error_data.details, plus an InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up. With InfiQ you send with an InfiQ API key; the Meta access token behind it belongs to InfiQ's connection to your WhatsApp Business Account. If this code reaches you, that connection needs attention: contact InfiQ support with the InfiQ_traceid rather than generating tokens yourself.

Send it through InfiQ

Frequently asked questions

Which permissions does the WhatsApp Cloud API need?+
Sending and receiving messages uses whatsapp_business_messaging; managing templates, numbers and account settings uses whatsapp_business_management. Many integrations need both.
Is error 3 the same as error 10?+
They're close. Meta describes 3 as a capability or permissions issue and 10 as a permission that wasn't granted or was removed. Check the token's permissions in both cases.
Will a new token fix error 3?+
Only if the new token carries the missing permission. A fresh token with the same grants fails the same way, so fix the app's permissions first.

Connect once, send without token juggling

Send with an InfiQ API key while InfiQ manages the connection to your WhatsApp Business Account.