Facebook Ads Insights API Error: Missing Capability?

Javid Jaffer on September 15, 2026

This error usually means the Facebook app you’re using doesn’t have the required permissions or access level to call the Ads Insights API.

A few things I’d check:

Ads Management Permission
- Make sure your app has ads_read or ads_management permissions approved and granted to the user making the request.
App Mode
- If the app is still in Development Mode, only users listed as admins, developers, or testers can access ad account data.
- For production use, the app typically needs to be switched to Live Mode.
Business Verification
- Some Marketing API features require Business Verification and Advanced Access for permissions.
Ad Account Access
- Verify that the Facebook user whose access token you’re using has access to the ad account you’re querying.
Access Token
- Check whether the token includes the required scopes. You can inspect it using Facebook’s Access Token Debugger.
API Version
- If you’re using older code, verify that the API version you’re are calling is still supported.

If the error message specifically says:

“Application does not have the capability to make this API call”

it’s most commonly caused by missing Advanced Access for ads_read/ads_management or attempting to use an app that hasn’t been approved for Marketing API access.

Could you share the exact error response (including the error code and subcode)? That usually makes it much easier to pinpoint the root cause.

Liked by

Reply

This error usually means the Facebook app you're using doesn't have the required permissions or access level to call the Ads Insights API. 
A few things I'd check: 
<ol> 
<li> 
Ads Management Permission 
<ul> 
<li> 
Make sure your app has ads_read or ads_management permissions approved and granted to the user making the request. 
</li> 
</ul> 
</li> 
<li> 
App Mode 
<ul> 
<li> 
If the app is still in Development Mode, only users listed as admins, developers, or testers can access ad account data. 
</li> 
<li> 
For production use, the app typically needs to be switched to Live Mode. 
</li> 
</ul> 
</li> 
<li> 
Business Verification 
<ul> 
<li> 
Some Marketing API features require Business Verification and Advanced Access for permissions. 
</li> 
</ul> 
</li> 
<li> 
Ad Account Access 
<ul> 
<li> 
Verify that the Facebook user whose access token you're using has access to the ad account you're querying. 
</li> 
</ul> 
</li> 
<li> 
Access Token 
<ul> 
<li> 
Check whether the token includes the required scopes. You can inspect it using Facebook's Access Token Debugger. 
</li> 
</ul> 
</li> 
<li> 
API Version 
<ul> 
<li> 
If you're using older code, verify that the API version you're are calling is still supported. 
</li> 
</ul> 
</li> 
</ol> 
If the error message specifically says: 
 
"Application does not have the capability to make this API call" 
 
it's most commonly caused by missing Advanced Access for ads_read/ads_management or attempting to use an app that hasn't been approved for Marketing API access. 
Could you share the exact error response (including the error code and subcode)? That usually makes it much easier to pinpoint the root cause.

Cancel

Subscriber

Sameena on September 9, 2026

The most common cause of this error is that the app doesn’t have the required Marketing API permissions or access level, even if the access token itself is valid.

If you’re calling the Insights endpoint directly, make sure to check:

The app is in Live Mode (not Development Mode).
The access token includes ads_read or ads_management permissions.
The user associated with the token has access to the ad account.
The app has been granted access to the Marketing API if required.
The ad account is linked to the correct Business Manager.

A quick way to troubleshoot is to use Facebook’s Access Token Debugger and verify that the token contains the necessary ad-related permissions. I’ve seen many cases where other Graph API endpoints work fine, but the Insights endpoint fails because the app lacks Ads API capabilities specifically.

I’d also try a simple test request against the ad account endpoint first before calling /insights to confirm that the issue is permission-related rather than an account access issue.

Liked by

Reply

The most common cause of this error is that the app doesn't have the required Marketing API permissions or access level, even if the access token itself is valid. 
If you're calling the Insights endpoint directly, make sure to check: 
<ul> 
<li> 
The app is in Live Mode (not Development Mode). 
</li> 
<li> 
The access token includes ads_read or ads_management permissions. 
</li> 
<li> 
The user associated with the token has access to the ad account. 
</li> 
<li> 
The app has been granted access to the Marketing API if required. 
</li> 
<li> 
The ad account is linked to the correct Business Manager. 
</li> 
</ul> 
A quick way to troubleshoot is to use Facebook's Access Token Debugger and verify that the token contains the necessary ad-related permissions. I've seen many cases where other Graph API endpoints work fine, but the Insights endpoint fails because the app lacks Ads API capabilities specifically. 
I'd also try a simple test request against the ad account endpoint first before calling /insights to confirm that the issue is permission-related rather than an account access issue.

Cancel

Subscriber

Miley on September 9, 2026

This error usually means the issue is not with the access token itself, but with the app’s permissions and Ads API access level.

A few things I’d check:

Ads API Access
- Ensure the app has been approved for the Marketing API/Ads API.
- Some endpoints, including Insights, require specific access levels that aren’t available to all apps.
Permissions
- Verify the token includes the required permissions such as:
  - ads_read
  - ads_management (if applicable)
- Re-generate the token after granting permissions.
App Mode
- If the app is in Development Mode, it can only access ad accounts belonging to app admins, developers, or testers.
- For production accounts, the app may need to be switched to Live Mode.
Business Manager Access
- Confirm the user generating the token has access to the ad account and that the app is associated with the correct Business Manager.
Token Validation
- Use Facebook’s Access Token Debugger to verify:
  - Token validity
  - Granted permissions
  - User and app association

In many cases, I’ve seen this error resolved by moving the app to Live Mode and ensuring the token has the proper ads_read permission. If you can share the Graph API version and app setup details, it would help narrow down the root cause.

Liked by

Reply

This error usually means the issue is not with the access token itself, but with the app's permissions and Ads API access level. 
A few things I'd check: 
<ol> 
<li> 
Ads API Access 
<ul> 
<li> 
Ensure the app has been approved for the Marketing API/Ads API. 
</li> 
<li> 
Some endpoints, including Insights, require specific access levels that aren't available to all apps. 
</li> 
</ul> 
</li> 
<li> 
Permissions 
<ul> 
<li> 
Verify the token includes the required permissions such as: 
<ul> 
<li> 
ads_read 
</li> 
<li> 
ads_management (if applicable) 
</li> 
</ul> 
</li> 
<li> 
Re-generate the token after granting permissions. 
</li> 
</ul> 
</li> 
<li> 
App Mode 
<ul> 
<li> 
If the app is in Development Mode, it can only access ad accounts belonging to app admins, developers, or testers. 
</li> 
<li> 
For production accounts, the app may need to be switched to Live Mode. 
</li> 
</ul> 
</li> 
<li> 
Business Manager Access 
<ul> 
<li> 
Confirm the user generating the token has access to the ad account and that the app is associated with the correct Business Manager. 
</li> 
</ul> 
</li> 
<li> 
Token Validation 
<ul> 
<li> 
Use Facebook's Access Token Debugger to verify: 
<ul> 
<li> 
Token validity 
</li> 
<li> 
Granted permissions 
</li> 
<li> 
User and app association 
</li> 
</ul> 
</li> 
</ul> 
</li> 
</ol> 
In many cases, I've seen this error resolved by moving the app to Live Mode and ensuring the token has the proper ads_read permission. If you can share the Graph API version and app setup details, it would help narrow down the root cause.

Cancel