Meta ads API access: how to get it for your own ad accounts
TofuAnswer by the Tofu team · checked
You can start reading your own Meta ad accounts through the Marketing API without App Review. Create a business app in Meta's App Dashboard, connect it to your business portfolio and add a Marketing API use case. Business apps get standard access to ads_read automatically, and the app starts on Limited Access, which Meta calls "heavily rate-limited" and "for development only." For regular reporting, request Full Access, which Meta ties to App Review, once the app has made 500 Marketing API calls in 15 days with under 15% errors. Automated pulls use a system user token.
Ask Tofu next
Pick a question and Tofu Ads Agent answers it in chat.
- Show my Meta spend, leads and cost per lead by campaign for last month
- Which Meta Ads Insights fields should a B2B team pull into a weekly report?
- Do I need Full Access if I only pull Meta ads reports once a day?
- How do I give our agency API access to our Meta ad accounts?
- Pull my Meta and LinkedIn ad spend into one report by campaign
As of November 2026.
Before you start
- A Meta developer account. Meta's Marketing API guide lists it as a prerequisite.
- Admin access to the business portfolio that owns your ad accounts. Meta's business verification page says you can connect your app to a business "that you're an Admin of."
- Your ad account IDs. In Ads Manager, open the account's Settings; the number is in the Account overview section.
- Who will call the API. A person testing by hand can use their own token. A script that runs on a schedule should use a system user, which Meta says represents "servers or software making API calls to assets owned or managed by a Business Manager."
Step 1: Create a business app
- Go to developers.facebook.com/apps/creation, enter an app name and contact email, and click Next.
- Pick a use case. For reporting, choose Measure ad performance data with Marketing API. If the app will also create or change ads, choose Create & manage ads with Marketing API. Meta greys out use cases that can't be combined.
- Under Business, pick your business portfolio and click Next.
- Review the requirements, then click Go to dashboard.
Meta's use case page lists ads_read, ads_management and business_management among the permissions required for these use cases, along with the access tier feature under its old name, Ads Management Standard Access. Meta's authorization page says Limited Access is "Automatically granted when you add the Marketing API product to your app."
If you skipped the portfolio when you created the app, Meta's use case page says you can connect one later from Settings in the app's left-side menu.
Step 2: Check your access and add your team
In the App Dashboard, go to App Review, then Permissions and Features. Meta says business apps "are automatically approved for standard access for all permissions and features," and "If your app is only managing your ad account, standard access to the ads_read and ads_management permissions are sufficient."
Two rules shape who can use it:
- Only people with a role on the app. Meta says "Permissions with Standard Access can only be requested from app users who have a role on the requesting app." Add the teammates who will connect as Admin, Developer or Tester under app roles.
- No publishing or verification needed for this. Meta says "You only need to publish your app if your app will access data that you don't own or manage" (or uses a product that needs it, such as webhooks). Its business verification page says "If your app will only be used by app users who have a role on the app itself you do not need to complete verification."
Here's what each tier of the Marketing API Access Tier gives you, from Meta's authorization and rate limiting pages:
| Limited Access (default) | Full Access | |
|---|---|---|
| How you get it | Automatically, with the Marketing API product | Click +Upgrade for the Marketing API Access Tier feature once you qualify (Step 5) |
| Meta's summary | "Heavily rate-limited per ad account. For development only." | "Lightly rate limited per ad account." |
| Ad account score cap | 60 (a read call is 1 point, a write 3); then blocked for 300 seconds | 9,000; then blocked for 60 seconds |
| Hourly insights quota per ad account (before errors) | 600 + 400 per active ad | 190,000 + 400 per active ad |
| System users | 1, plus 1 admin system user | 10, plus 1 admin system user |
| Business Manager and Catalog APIs | Limited | All |
On May 4, 2026, Meta renamed the Ads Management Standard Access feature to the Marketing API Access Tier: Standard Access became Limited Access, and Advanced Access became Full Access. Existing access carried over, and Meta said no code changes were needed. Some Meta pages still use the old names.
Step 3: Get an access token
Every Marketing API call needs an access token.
- To test: open the Graph API Explorer, choose your app, pick the user token option, add
ads_readand click Generate Access Token. This token is for trying calls by hand. - For automated reporting: use a system user token. Meta's authentication guide says these are "useful for server-to-server interactions where there is no user present to authenticate." Our page on Meta access tokens that never expire shows how to create one.
Step 4: Pull your first report
Ad account IDs take an act_ prefix in the API. A first call for last week's spend looks like this:
GET https://graph.facebook.com/v27.0/act_<AD_ACCOUNT_ID>/insights?fields=spend,impressions,clicks&date_preset=last_7d
- You need
ads_read. Meta lists it as the permission for the Ads Insights API. - Without a date, you get about a month. Meta says GET requests return basic metrics "typically from the past 30 days."
- Pick the level. The
levelparameter returns results byaccount,campaign,adsetorad. Meta's rate limiting page says to "use Level Parameters or filtering to reduce the number of calls." - Run big pulls as async jobs. Meta says to use asynchronous requests "to query a huge amount of data." A POST to
/act_{ad_account_id}/insightscreates a report run you collect later. - Count your calls. Each successful call counts toward Full Access, and errors count against it.
Step 5: Request Full Access when you need it
Meta describes Limited Access as for development only. Before you run reporting in production, or once you hit its limits, check Meta's requirements for Full Access:
- "Have successfully made at least 500 Marketing API calls in the last 15 days."
- "Have made Marketing API calls with an error rate of less than 15% in the last 500 calls."
In its May 4, 2026 update, Meta cut the call count from 1,500 to 500, measured errors over your last 500 calls instead of a fixed period, and said "the screen recording upload is no longer required." It also said the requirements now show in the App Dashboard under Permissions & Features, and your progress shows on the allowed usage page when you edit the request. When you qualify, click +Upgrade for the Marketing API Access Tier feature.
Meta's pages agree that Full Access goes through App Review but differ on what that involves. The authorization page labels it "Full access (after App Review)" and says "Your tier is determined by whether your app has been approved through App Review." But the use case page, which still uses the old feature name, says the higher tier "requires approval through App Review with other annual reviews to maintain it," and its App Review steps still ask you to upload a screen recording for each permission or feature, which the May 4 blog says is no longer needed. Check the dashboard for what your request asks for.
On business verification, Meta's authorization page says it's required "if your app will access sensitive data," and doesn't list it among the Full Access requirements.
Common problems
| Problem | Why it happens | Fix |
|---|---|---|
| Error 17, "User request limit reached" | Your calls to one ad account hit its score limit, which is 60 on Limited Access | Wait, cut calls with level and filtering, use async jobs, then request Full Access |
| Error 80000, 80003, 80004 or 80014, "too many calls from this ad-account" | The ad account's quota is used up | Meta says to "scale back the changes to the ad account." Space out calls |
| A teammate can't authorize the app | Standard access only works for people with a role on the app | Add them under app roles |
| You don't qualify for Full Access yet | Fewer than 500 successful calls in the last 15 days, or an error rate of 15% or more over your last 500 calls | Keep calling and fix failing requests, then check your progress in the dashboard |
| You also need clients' ad accounts | Meta says other people's accounts need advanced access to ads_read and/or ads_management, and "Advanced Access now requires Business Verification" | Plan for App Review and verifying your business |
| The token stopped working | Tokens can expire or be revoked | See Meta access tokens that never expire |
| You'd rather not write code | For AI assistants, see Meta's ads MCP server. For spreadsheets and dashboards, see cheaper alternatives to Supermetrics |
Sources (14)
- Marketing API Authorization (Meta for Developers), checked November 19, 2026
- Update to Ads Management Standard Access: New Name, Revised Requirements, and More Transparency (Meta for Developers blog, May 4, 2026), checked November 19, 2026
- Marketing API Rate Limiting (Meta for Developers), checked November 19, 2026
- Get started with the Marketing API (Meta for Developers), checked November 19, 2026
- Create an App (Meta for Developers), checked November 19, 2026
- Marketing API Use Cases (Meta for Developers), checked November 19, 2026
- Access Levels (Meta for Developers), checked November 19, 2026
- Business Verification (Meta for Developers), checked November 19, 2026
- Marketing API Authentication (Meta for Developers), checked November 19, 2026
- System Users (Meta for Developers), checked November 19, 2026
- Permissions Reference for Meta Technologies APIs: ads_read (Meta for Developers), checked November 19, 2026
- Ads Insights API (Meta for Developers), checked November 19, 2026
- Ad Account Insights reference (Meta for Developers), checked November 19, 2026
- Ad Account reference (Meta for Developers), checked November 19, 2026