Getting Started
Resolve a brand to an advertiser, pull its ads, then follow one ad through to its creative files.
1. Get your API key
Create an account and generate a FetchLayer API key from your dashboard. There is no Google Cloud project to set up, no OAuth consent screen, and no Google Ads API developer token to apply for.
Create free account →2. Resolve the brand to an advertiser
Google organises its transparency data by advertiser, so almost everything starts with an advertiser id. Several distinct advertisers can share a brand name — a global company often registers one per market — so compare the verified country and the approximate ad count to pick the right one.
curl -X POST https://api.fetchlayer.dev/google-ad-library/search-advertisers \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"query":"Nike","region":"US","limit":10}'3. Pull that advertiser's ads
curl -X POST https://api.fetchlayer.dev/google-ad-library/advertiser-ads \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"advertiser":"AR01234567890123456789","region":"US","surfaces":["youtube","search"],"limit":50}'There is no keyword search over ad copy
/search-ads takes a brand name or a website, resolves it to advertisers, and returns their ads — it reports what it matched on matchedAdvertisers. Once you hold an advertiser id, use /advertiser-ads instead: it skips resolution entirely, so the wrong company can never be matched. 4. Follow an ad to its creative
Every ad carries an adId and an advertiserId. Google needs both to locate an ad, so pass the pair — or pass the full Ad Library ad URL, which already carries them.
curl -X POST https://api.fetchlayer.dev/google-ad-library/ad-media \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"ad":"CR01234567890123456789","advertiser":"AR01234567890123456789","kinds":["video","image"],"probe":true}'Tip
downloadUrl, not its raw url. Google's own video URLs are signed, expire, and only play back from the address they were issued to. GET /media is the one endpoint that takes query parameters instead of a JSON body, and it supports HTTP Range requests — so a video streams and seeks in a player instead of downloading whole. 5. Check the notes before you trust the totals
Every response carries a notes array. It reports what is specific to that result — a page walk that stopped short of what you asked for, a listing that may be incomplete, run dates that could not be resolved. Alongside it, approximateTotal is a { min, max } range, not an exact count: Google never publishes an exact figure. A quiet, well-formed, partial answer is the failure mode to guard against.