Facebook ads library api

Google ranks 'facebook ad library api' (singular) and 'facebook ads library api' (plural) as related-but-distinct queries. Search intent differs subtly: singular phrasing tends to come from people thinking about the tool conceptually ('what is the Ad Library API'); plural phrasing tends to come from people already thinking about query workflows ('I'm going to be pulling many ads via this API'). Same product, marginally different audience mindset, different optimal landing page.

We maintain a guide per variant so whichever phrasing you typed, you land on a clean page rather than getting bounced through a SERP optimized for the other variant. The technical content is largely the same; the framing leans into the audience's mindset.

If you want the singular-variant version, see our Facebook Ad Library API guide. Everything below applies to both variants - same product, same endpoints, same gates.

Meta's commercial-ad API coverage is bound by the regulatory regimes that mandated the disclosure. EU member states are covered because the Digital Services Act (DSA) requires Very Large Online Platforms to maintain queryable repositories of all advertising shown to EU users. Brazil is covered because Brazilian election and advertising transparency law requires similar disclosure. No other jurisdiction has mandated commercial-ad disclosure at the same level, so Meta has not extended the API's commercial coverage.

The practical workflow split: if your competitive set runs ads in the EU or Brazil, you can query their commercial data programmatically by setting ad_reached_countries to those regions. If your competitive set runs only in non-covered regions, the API returns political ads only (typically empty for commercial brands).

Workaround for non-EU/Brazil markets: route research through EU-targeted queries when the competitor is multinational. A US brand that also runs ads in Germany will have those German-targeted ads exposed via the API. Use the German data as a proxy for global creative strategy. Imperfect (creative may be localized) but sanctioned and structured.

The 200-calls/hour/token rate limit is the operational bottleneck most teams hit first. Three patterns work in production. Multi-token rotation: maintain 4-8 access tokens (each on a separate App, all owned by the same Business Manager) and rotate calls across them. The limit is per-token, not per-app. Aggressive caching: most competitive monitoring queries don't need real-time data. Cache responses 12-24 hours and serve from cache rather than re-hitting the API. Incremental queries: instead of refetching a competitor's full ad set every run, query only ad_delivery_date_min={yesterday} to get new launches; full re-fetch weekly. Cuts call volume by 90%+ for steady-state monitoring.

If you have a documented use case (research project, agency client deliverable, internal product), you can request a quota increase through the App dashboard. Meta rarely denies legitimate requests but adds a 1-2 week review cycle. For most agencies and research projects, the rate limit is a real constraint worth planning around rather than ignoring.

Plan your retry logic carefully. The API returns 429 on rate-limit hits; build exponential backoff with jitter (start at 5s, max 5 min) and respect the Retry-After header where Meta provides it. Naive retry-without-backoff makes the rate-limit problem worse, not better.

Three viable paths in 2026. The API is right when you're operating in EU/Brazil markets, you need clean structured data, you can absorb the verification timeline, and you can engineer around the rate limits. Strong fit for academic research, regulatory-compliance audits, and EU-focused competitive monitoring.

UI scraping is the de facto path outside EU/Brazil for commercial-ad research. Against Meta's TOS, exposes you to IP blocks and DOM-change breakage, requires real engineering investment. Most teams that go this route eventually move to a paid tool because the maintenance burden compounds. See our scraper guide for the full options.

Third-party tools (Foreplay, Atria, Motion, AdSpy, Minea) maintain the scrape infrastructure professionally and resell access at $50-500/mo. For competitive marketing teams this is almost always the right choice over building yourself - you get the data plus the tagging layer plus the maintenance team without the engineering burden. Pair with the official API for EU/Brazil markets if you need structured exports for academic or compliance use cases.

Internal: Foreplay deep dive, Atria deep dive, Motion deep dive.