TikTok Ads Library Scraper — Commercial Content API

Scrape TikTok's Commercial Content Library via the official open.tiktokapis.com API. Search ads by keyword or advertiser business ID across EU/EEA/UK regions. Returns creatives, video URLs, reach estimates, targeting data, and advertiser metadata — all via the official API, which never breaks on DOM changes.

Why this actor over alternatives?

Feature	This actor	Typical DOM scrapers
Official API	Yes — open.tiktokapis.com	No — scrapes library.tiktok.com HTML
Stability	Never breaks on UI changes	Breaks when TikTok redesigns UI
parse_confidence	Yes — per-record data quality score	No
Targeting data	Yes — age/gender/location/interests	Rarely
Per-country reach	Yes (via includeDetails)	No
Proxy needed	No — official API	Usually yes ($$$)

Input

Field	Required	Description
accessToken	Yes	TikTok client access token (clt.xxx). Get via research program.
keywords	One of these	Keywords to search ad copy for. Each runs as a separate query.
advertiserBusinessIds	One of these	Numeric advertiser business IDs to look up directly.
countryCode	No	Two-letter country code or ALL. EU/EEA/UK only. Default: ALL.
dateFrom	No	Start date, format YYYYMMDD. Minimum: 20221001.
dateTo	No	End date, format YYYYMMDD. Default: today.
searchType	No	exact_phrase (default) or fuzzy_phrase.
maxItems	No	Cap results per keyword. Leave blank = unlimited.
includeDetails	No	Fetch full targeting + per-country reach (doubles requests).

Output schema

Each result row is a flat JSON object:

{
  "ad_id": "1923845247192304",
  "advertiser_name": "Nike EU",
  "advertiser_id": "3847236290405",
  "advertiser_paid_by": "Nike, Inc.",
  "region": "FR",
  "first_shown": "2024-01-01",
  "last_shown": "2024-12-31",
  "status": "active",
  "impressions_range": "11K",
  "video_url": "https://cdn.tiktokcdn.com/video123.mp4",
  "image_urls": [],
  "caption": null,
  "ad_url": "https://library.tiktok.com/ads?adId=1923845247192304",
  "query": "nike",
  "parse_confidence": 1.0,
  "warnings": []
}

With includeDetails: true, additional fields:

{
  "targeting_countries": ["FR", "DE"],
  "targeting_age": {"18-24": true, "25-34": true},
  "targeting_gender": {"female": true, "male": true},
  "targeting_audience_size": "50K",
  "targeting_interests": "Sports, Fitness",
  "reach_by_country": {"FR": "8K", "DE": "3K"},
  "advertiser_profile_url": "https://www.tiktok.com/@nike",
  "advertiser_avatar_url": "https://p16.tiktokcdn.com/avatar.jpeg",
  "advertiser_follower_count": 1200000
}

Supported regions

EU/EEA/UK only — TikTok's Commercial Content API covers: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Iceland, Liechtenstein, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, United Kingdom, Switzerland.

Use countryCode: "ALL" to search across all supported regions simultaneously.

Getting an access token

TikTok's Commercial Content API requires an approved research account:

1. Apply at developers.tiktok.com → Research API
2. Once approved, get your client_key and client_secret
3. Exchange for an access token:

curl -X POST https://open.tiktokapis.com/v2/oauth/token/ \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "client_key=YOUR_KEY&client_secret=YOUR_SECRET&grant_type=client_credentials"

The response contains an access_token (prefixed clt.) — pass this as accessToken input.

FAQ

Why EU/EEA/UK only? TikTok's Commercial Content Library is a transparency measure under the EU Digital Services Act (DSA). Coverage is limited to these jurisdictions by TikTok's API design.

What is parse_confidence? A score from 0.0 to 1.0 indicating data quality for each record. 1.0 = all expected fields present. Below 0.5 = critical fields missing — check warnings for which ones.

What does impressions_range mean? TikTok returns audience reach as bucketed ranges (e.g., "11K", "100K–200K") rather than exact counts, by design. This is the raw value from the API.

Can I get ad creative text / copy? The TikTok Commercial Content API does not expose ad body copy directly. The caption field is extracted from rejection reason text when present. For creative copy, use TikTok's Creative Center separately.

Data since when? TikTok's Commercial Content Library covers ads from October 1, 2022 onward.

---

Not affiliated with TikTok, ByteDance, or their subsidiaries. All data is retrieved from TikTok's public official API.

Integrations

Built for ad-intelligence researchers and compliance teams with TikTok API access auditing EU/EEA ad creatives and targeting — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.