Ad Library APIs Compared: Meta vs TikTok vs Google vs OpenAdLibrary

An ad library API gives you programmatic access to an ad-transparency dataset — the ads themselves plus metadata like advertiser, run dates and sometimes spend — so you can build monitoring pipelines, research tools or AI agents instead of clicking through a web UI. In 2026 four options matter: the Meta Ad Library API (official, gated behind identity verification, deepest for political and EU-served ads), TikTok's Commercial Content Library API (official, EU-scoped, research-oriented), Google's political-ads dataset (official but narrow — the Ads Transparency Center itself has no public API), and the OpenAdLibrary API (independent, covering the native/open-web networks that publish no official library at all). They differ sharply in access friction, coverage and fields, so the right choice is mostly a function of which channel you need to see.

What counts as an ad library API — and who needs one#

An ad library is a searchable archive of ads a platform has served; the API version is the same corpus exposed as structured data. Typical consumers:

• Competitive-intelligence pipelines — nightly pulls of a competitor set into your own warehouse or dashboard.
• Researchers and journalists — election-spend analysis, platform-accountability studies, ad transparency audits.
• Brand-protection and compliance teams — detecting affiliate misuse, fake endorsements and copycat funnels at scale.
• Product builders — anyone shipping a feature that needs live ad data behind it.
• AI agents — LLMs that answer "what is brand X running right now?" need an API (or MCP server) underneath.

One thing worth knowing before you evaluate anything: most commercial ad-spy products expose data only through their UI. Genuine API access is rare enough that we keep a separate shortlist of ad spy tools with an API.

Meta Ad Library API#

The official Meta Ad Library API is the most established option, and the most gated. Access requires a Facebook developer account plus an identity-verification step, and the process takes real time — plan days, not minutes.

What you get once in: keyword and Page search across the library, with data depth that varies by ad category and region. Ads about elections, politics and social issues return spend bands, impression ranges and demographic breakdowns. Ads delivered to EU users carry Digital Services Act fields — reach and targeting summaries. Ordinary commercial ads outside the EU return the creative, dates and placements but no performance-adjacent numbers, and generally leave the dataset once inactive.

The practitioner frictions are predictable: verification hoops, per-token rate limits, thin commercial coverage outside the EU, and no landing-page or funnel data. It is the right tool for political-ads research and EU-scoped analysis; it is a partial tool for competitive intelligence. Field definitions and terms change — check Meta's current documentation before you design a schema around it.

TikTok Commercial Content Library API#

TikTok's Commercial Content Library is a DSA-era transparency surface covering ads and commercial content delivered to the EU (plus some adjacent markets). The API behind it is aimed at researchers and requires an application; approval is not instant and not universal.

Coverage is the main constraint: if your question is about EU-served TikTok ads, this is the official answer. If your question is about the US, or about performance, it mostly is not — you get advertiser identity, dates, reach ranges and targeting summaries for in-scope ads, and nothing for out-of-scope regions. As with Meta, treat the current TikTok documentation as the source of truth on fields and eligibility.

Google: transparency without an API#

Google's Ads Transparency Center is a web UI — there is no general public API for it. What exists programmatically is narrower: Google publishes a political-advertising dataset (spend, advertiser and targeting data for election ads in covered regions) as a public BigQuery dataset, which is excellent for its purpose and useless for commercial competitive research.

For ordinary Google ads there is no official programmatic access at all. Scraping the Transparency Center violates terms of service and breaks routinely, so most teams simply accept the gap — or cover the open web from the supply side instead.

OpenAdLibrary API: the open web's ad library#

The native advertising ecosystem — Taboola, Outbrain, MGID, Revcontent, MediaGo, the Microsoft Audience Network — publishes no official ad library whatsoever. OpenAdLibrary fills that gap independently, by continuously capturing live public placements, resolving the advertiser behind each ad, and tracing the click through to the landing page.

The corpus behind the API, as of July 2026: 725,000+ live native ad creatives across 49 networks from 29,000+ advertisers, backed by 6.8 million+ ad observations and 1.3 million+ captured landing pages.

The API itself is a REST surface (/api/v1) with self-serve key auth — no application process, no identity verification. You can search ads by keyword, advertiser, network, vertical, geo and device; per-creative fields include the full-quality image, headline, network, first-seen/last-seen dates, resolved brand and the traced landing URL. Free keys carry a small daily request cap for evaluation; the paid plan ($29.99/mo) raises limits — see pricing for current quotas, and the native ad data API overview for the field-by-field reference.

Two OpenAdLibrary-specific angles worth noting:

• Longevity as a first-class field. Because capture is continuous, first-seen/last-seen dates come with every creative — the closest public proxy for "this ad is profitable," and something none of the official APIs expose for commercial ads.
• An MCP server for agents. The same corpus is exposed as tools at mcp.openadlibrary.com for Claude, ChatGPT and other MCP clients. If your "API consumer" is an LLM, the MCP route skips the HTTP plumbing entirely.

Side-by-side comparison#

Practical notes before you build#

A few things that bite developers on their first ad-library integration, regardless of vendor:

• Diff, don't dump. The useful signal is change — new creatives, stopped creatives, new advertisers in a vertical. Pull a fixed set on a schedule and diff against your last snapshot rather than re-ingesting the world.
• Archive creatives you care about. Image URLs in any ad dataset can rot as CDNs expire assets. If a creative matters to your analysis, store your own copy at fetch time.
• Respect the quotas. Every option here rate-limits. Design for backoff on day one, and batch queries by advertiser rather than issuing one call per creative.
• Read the terms. Regulatory APIs in particular restrict redistribution and commercial reuse of their data — what you may store, display and resell differs by source.

Choosing by use case#

• Political or election research → Meta Ad Library API plus Google's political dataset. This is what they were built for, and the spend data is real.
• EU platform-compliance research → TikTok CCL plus Meta's DSA fields.
• Social competitive monitoring → Meta's API, accepting the verification hoop and thin non-EU commercial data.
• Native and open-web competitive intelligence — affiliate research, funnel analysis, brand protection — → OpenAdLibrary, because no official source covers these networks at all.
• Agent and LLM workflows → MCP first, REST as fallback.

The honest summary: official ad library APIs are regulatory artifacts — deep exactly where regulation forced depth (political ads, EU delivery) and shallow everywhere else. If the ads you care about run on the open web, the independent route is not the compromise option; it is the only option.