Facebook营销API报错#3：测试账号无法调用API的问题排查

Let’s break down your issues one by one to get you sorted out:

1. Why your personal account works but test accounts don’t #

The key difference here boils down to account access and app context:

• Your personal account is likely linked to an active Facebook Ad Account where you hold admin/editor privileges, and it’s either listed as a developer/admin of your app or your app is in live mode (allowing your verified account to access restricted permissions).
• Test accounts need two critical pieces to work with ad-related APIs:
  • They must be added as test users in your Facebook Developer App Dashboard (under Roles > Test Users).
  • The test account must have explicit access to an Ad Account—either create a test Ad Account tied to the test user, or add the test user as a role (admin/editor/analyst) on an existing account via Ads Manager. Without this, even if your app has permissions, the test user can’t perform ad-related actions.

2. Can you request ads_read and ads_management via the Facebook JS SDK? #

Absolutely! You just need to include these permissions in the scope parameter when initiating the login flow. Here’s a quick example:

FB.login(function(response) {
  if (response.authResponse) {
    console.log('Login successful - token acquired!');
    // Proceed with your API calls here
  } else {
    console.log('Login cancelled or failed.');
  }
}, { scope: 'ads_read,ads_management' });

Important note: These are review-required permissions. While you can test them with internal users (developers, admins, test users) in development mode, you’ll need to submit your app for Facebook’s App Review if you want to use them with external users. The review requires you to demonstrate exactly how your app uses these permissions in compliance with Facebook’s Platform Policies.

3. Why can you call /v2.12/me/adaccounts but other ad APIs fail? #

The /me/adaccounts endpoint is relatively permissive—it only requires the ads_read permission and that the user has access to at least one Ad Account. The error (#3) Application does not have the capability to make this API call for other APIs usually points to one of these issues:

• Missing specific permissions: Some ad-related APIs (like creating ads, updating campaigns) require ads_management instead of just ads_read. Double-check the API documentation for the endpoint you’re trying to use to confirm the required permissions.
• Token scope mismatch: Verify your access token actually includes the permissions you need. You can check this by calling the debug_token endpoint:

  curl -X GET "https://graph.facebook.com/v2.12/debug_token?input_token=YOUR_USER_ACCESS_TOKEN&access_token=YOUR_APP_ID|YOUR_APP_SECRET"
  

• App capability restrictions: Certain advanced ad APIs require your app to be approved for additional capabilities (e.g., Marketing API access tiers). Check your App Dashboard under Products > Marketing API to ensure you have the necessary access levels.
• Ad Account role limitations: Even if your token has ads_management, the test user might only have a "Viewer" role on the Ad Account, which prevents modifying or creating ads. Confirm the test user’s role in Ads Manager (Settings > Ad Account Roles).

内容的提问来源于stack exchange，提问作者MasterSinge