Ad data for your product, from one API.
Ad spy tools, creative research apps and AI agents all need the same thing underneath: reliable ad data from every library, in one shape, with history. We run the collection, the archive and the webhooks; your team builds the features your customers pay for.
- Ad intelligence and creative research SaaS
- AI products that answer questions about ads
- Teams replacing an in-house scraper
The problem
Six formats to maintain
Each library has its own data format, session rules and blocking. Keeping all six running is a team's full-time job.
History you can't backfill
Ads that ended before you started crawling are gone from most libraries. Every month without an archive is data you can't recover.
Matching accounts to companies
Customers search by brand or domain, while the libraries index pages and advertiser IDs. The mapping is its own product.
How it works with AdLib
- 01
One schema for every platform
Search, ads, advertisers and history come back in the same fields whatever the source, documented in OpenAPI 3.1.
curl "https://api.adlibapi.com/v1/search?domain=acme.com&platform=meta,tiktok&status=active" \ -H "X-API-Key: $ADLIB_API_KEY" - 02
History and change events
Every ad keeps its creative versions and active periods. Watchlists send your backend advertiser.changes events, so your product can alert its own users.
- 03
Domain resolution built in
Your users type a brand or domain; we return the matching accounts on each platform with scores and evidence, and you can report wrong matches back.
What it costs
That is about $0.50 per 1,000 Meta ads on Business. Redistributing raw data inside a data product needs Enterprise terms; talk to us.
See plans and credit packs- Ads
- 1 credit (Meta, TikTok, Pinterest, X), 2 (Google), 3 (LinkedIn)
- Cached results and platform errors
- Free
- Business plan
- 1.6M credits a month for $799
Questions
- Is there an API for all ad libraries in one place?
- Yes. AdLib returns ads from the public ad libraries of Meta, Google, TikTok, LinkedIn, Pinterest and X in one schema, with an archive of ads that stopped running.
- Should I build my own ad library scraper?
- Build it if ad collection is your core product and you can staff its maintenance. Otherwise the cost is mostly ongoing: proxies, blocking, format changes on six platforms, and history you cannot backfill once you start late.
- Can I resell AdLib data in my product?
- You can build features on it for your users. Reselling or redistributing raw data as a dataset needs Enterprise terms.