Facebook Ads Insights API Error: Missing Capability?

Unfollow Follow

Kapil

Updated 21 hours ago in

Alteryx

I’m trying to fetch data from the Facebook Ads Insights API, but every request returns the following error:

{
  "error": {
    "message": "(#3) Application does not have the capability to make this API call",
    "type": "OAuthException",
    "code": 3
  }
}

The app has a valid access token, and I can successfully make requests to other Facebook Graph API endpoints.

Example request:

GET https://graph.facebook.com/v2.8/act_<AD_ACCOUNT_ID>/insights
  ?fields=impressions,clicks,spend
  &access_token=<ACCESS_TOKEN>

Has anyone encountered this issue with the Insights API specifically?

I’m wondering if this is related to:

Missing app permissions
App review requirements
Ads API access approval
Business Manager configuration

What was the actual fix in your case?

<p class="PDq2pG_selectionAnchorContainer" data-start="89" data-end="196">I’m trying to fetch data from the Facebook Ads Insights API, but every request returns the following error:</p>
<div class="relative w-full mt-4 mb-1">
<div class="">
<div class="contents">
<div class="border border-token-border-light border-radius-3xl corner-superellipse/1.1 rounded-3xl">
<div class="relative h-full w-full border-radius-3xl bg-(--code-block-surface) corner-superellipse/1.1 overflow-clip rounded-3xl [--code-block-surface:var(--bg-elevated-secondary)] dark:[--code-block-surface:var(--composer-surface-primary)] lxnfua_clipPathFallback">
<div class="relative">
<div class="h-full min-h-0 min-w-0">
<div class="h-full min-h-0 min-w-0">
<div class="">
<div class="relative">
<div class="">
<div class="relative z-0 flex max-w-full">
<div id="code-block-viewer" class="q9tKkq_viewer cm-editor z-10 light:cm-light dark:cm-light flex h-full w-full flex-col items-stretch ͼd ͼr" dir="ltr">
<div class="cm-scroller">
<pre class="cm-content q9tKkq_readonly m-0"><code>{
  "error": {
    "message": <span class="ͼk">"(#3) Application does not have the capability to make this API call"</span>,
    "type": <span class="ͼk">"OAuthException"</span>,
    "code": <span class="ͼj">3</span>
  }
}</code></pre>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="">
<div class=""> </div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p data-start="362" data-end="471">The app has a valid access token, and I can successfully make requests to other Facebook Graph API endpoints.</p>
<p data-start="473" data-end="489">Example request:</p>
<div class="relative w-full mt-4 mb-1">
<div class="">
<div class="contents">
<div class="border border-token-border-light border-radius-3xl corner-superellipse/1.1 rounded-3xl">
<div class="relative h-full w-full border-radius-3xl bg-(--code-block-surface) corner-superellipse/1.1 overflow-clip rounded-3xl [--code-block-surface:var(--bg-elevated-secondary)] dark:[--code-block-surface:var(--composer-surface-primary)] lxnfua_clipPathFallback">
<div class="relative">
<div class="h-full min-h-0 min-w-0">
<div class="h-full min-h-0 min-w-0">
<div class="">
<div class="relative">
<div class="">
<div class="relative z-0 flex max-w-full">
<div id="code-block-viewer" class="q9tKkq_viewer cm-editor z-10 light:cm-light dark:cm-light flex h-full w-full flex-col items-stretch ͼd ͼr" dir="ltr">
<div class="cm-scroller">
<pre class="cm-content q9tKkq_readonly m-0"><code>GET https://graph.facebook.com/v2.8/act_<AD_ACCOUNT_ID>/insights
  ?fields=impressions,clicks,spend
  &access_token=<ACCESS_TOKEN></code></pre>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="">
<div class=""> </div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p data-start="635" data-end="704">Has anyone encountered this issue with the Insights API specifically?</p>
<p data-start="706" data-end="742">I’m wondering if this is related to:</p>
<ul data-start="743" data-end="853">
<li data-section-id="yw1gfp" data-start="743" data-end="768">Missing app permissions</li>
<li data-section-id="nljz33" data-start="769" data-end="794">App review requirements</li>
<li data-section-id="aipxl1" data-start="795" data-end="820">Ads API access approval</li>
<li data-section-id="lhodpp" data-start="821" data-end="853">Business Manager configuration</li>
</ul>
<p data-start="855" data-end="892" data-is-last-node="" data-is-only-node="">What was the actual fix in your case?</p>

Cancel

2
15
21 hours ago
0

Reply

Write your reply here to join the conversation

YOUR PREVIEW

Avatar

Sameena 5 hours ago

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

<p>The most common cause of this error is that the app doesn't have the required <strong>Marketing API permissions or access level</strong>, even if the access token itself is valid.</p><br />
<p>If you're calling the Insights endpoint directly, make sure to check:</p><br />
<ul><br />
<li><br />
<p>The app is in <strong>Live Mode</strong> (not Development Mode).</p><br />
</li><br />
<li><br />
<p>The access token includes <strong>ads_read</strong> or <strong>ads_management</strong> permissions.</p><br />
</li><br />
<li><br />
<p>The user associated with the token has access to the ad account.</p><br />
</li><br />
<li><br />
<p>The app has been granted access to the Marketing API if required.</p><br />
</li><br />
<li><br />
<p>The ad account is linked to the correct Business Manager.</p><br />
</li><br />
</ul><br />
<p>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.</p><br />
<p>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.</p>

Cancel

Miley 5 hours ago

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

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

Cancel