Meta Ad Library API Access: What No App Review Actually Means (and Where People Still Get Stuck) (2026)
The Meta Ad Library API, the /ads_archive Graph API endpoint, is the only officially sanctioned way to pull data out of Meta's public ad archive at scale. Competitive-research tools, compliance monitors, and political-ad transparency projects all sit on top of it. It also breaks the pattern every other Meta permission follows, and that is exactly where teams building on it start making expensive assumptions.
The One Everyone Gets Backwards
What people expect
Like ads_management and ads_read on the Marketing API, or catalog_management, most Meta permissions require a formal App Review submission: use case description, screencast, data-handling explanation, and a review queue.
What's actually true
The Ad Library API does not require App Review. Your app unlocks /ads_archive by accepting Meta's Authorized Access to Public Information terms, because the data returned is public archive information, not private user or ad-account data.
Teams that assume this needs the same review packet as every other Meta API either lose weeks preparing a submission nobody asked for, or, worse, skip the step that actually is required because they assumed no App Review meant no gate at all.
The Step That Actually Gates You
Identity verification, not business verification
What does gate access is identity verification at the personal Facebook-account level (facebook.com/ID): government ID upload, country confirmation, and a review window measured in business days. This exists because the archive includes political and social-issue ad data, and Meta ties that sensitivity to a verified real person, not a verified business. For agencies or teams that want shared, non-personal access, this is the real complication: verification is tied to whichever account generates the token, with downstream implications for who can regenerate it later.
How Access Actually Comes Together
Identity and country verification
Completed at the personal account level before any app or token exists.
App setup and terms acceptance
Adding the Ad Library API product to a developer app and accepting the Authorized Access to Public Information terms.
Token generation and exchange
Short-lived tokens are issued first; production use needs the long-lived exchange.
Building a compliant query
ad_reached_countries is required on every call, and several filters, bylines, delivery_by_region, audience-size ranges, only apply to POLITICAL_AND_ISSUE_ADS, not the general archive.
Staying inside the operating limits
Rate-limit ceilings, parameter validation, and the no-resale/no-ad-targeting restriction Meta actively enforces on this data.
What Getting This Right Actually Looks Like
- Zero App Review submissions filed for an endpoint that never needed one, confirmed against Meta's own Ad Library API access terms, not a third-party guide.
- One identity-verified account and one long-lived token in place, no repeated approval cycles to maintain access.
- Query parameters scoped correctly from day one, so a project isn't built around fields (bylines, region, audience size) that only work for political/issue ads.
Where This Actually Breaks
Most stalls here aren't rejections, they're self-inflicted. The two patterns that show up most: preparing an App Review packet for an endpoint that doesn't use one, and assuming no App Review means no verification at all, then hitting a silent invalid-token error because identity verification was never completed. A close third: using archive data to build ad-targeting or a resale product, an explicit violation of Meta's access terms that can get a token or app pulled. This is the kind of setup where getting the sequence right the first time, rather than guessing from a third-party tutorial, is the entire value: see our Facebook App Review support if a broader Meta integration also needs standard permission review.
Frequently Asked Questions
Do I need Meta App Review to use the Ad Library API?
No. Accessing /ads_archive requires accepting Meta's Authorized Access to Public Information terms, not a standard App Review permission submission. Other work on the same app, such as Marketing API access or Page permissions, may still need App Review separately.
Do I need Meta Business Verification for this?
The Ad Library API's own access gate is personal identity verification at facebook.com/ID, not Business Manager verification. If a broader project also touches Business Manager assets, that is a separate, unrelated step.
Is the Ad Library API free to use?
Yes, there is no paid tier for the endpoint itself.
What happens if I hit the rate limit?
Meta returns error code 613. The fix is reducing request frequency, not resubmitting for a higher access tier, since there isn't one.
Can this data be resold or used for ad targeting?
No. Meta's access terms explicitly prohibit reselling archive data or using it to build ad targeting, and violating this risks the token or app being revoked.
Why does my query return zero results?
ad_reached_countries is mandatory on every call, and filters like bylines or audience-size ranges only apply when ad_type is set to POLITICAL_AND_ISSUE_ADS.
Meta makes all access, identity-verification, and enforcement decisions for the Ad Library API independently. This content is not affiliated with or endorsed by Meta Platforms, Inc., and specific verification timelines, access outcomes, or platform-policy changes cannot be guaranteed. Facts referenced above were verified against Meta's official Graph API reference and developer documentation as of 2026-07-19.