TikTok top ads (Creative Center)

GET https://api.api.sh/tiktok/v1/ad-library/top-ads
1 credit / call ad libraries try it in the playground →

The best-performing auction ads from TikTok Creative Center's Top Ads for a country and period, with each ad's title, brand, industry, objective, likes, CTR, video (cover, duration, size, playable video links) and a link to its Creative Center page. Sort by For You, likes, CTR, conversion rate, impressions or 2s/6s view rate; filter by industry, objective, ad language and likes band. Logged out, TikTok shows the first 20 ads of each filter combination (no further pages), so narrow with filters to see others. total is TikTok's count for the combination; available_filters lists the countries, industries and languages it offers. Video links expire after a few hours.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
country string Two-letter country code (default US); see available_filters.countries. Example: US
period 7 | 30 | 180 Days to rank over: 7, 30 (default) or 180. Example: 30
order_by for_you | likes | ctr | cvr | impressions | play_2s_rate | play_6s_rate Sort: for_you (default), likes, ctr, cvr, impressions, play_2s_rate, play_6s_rate. Example: for_you
industry string Industry ids, comma-separated (11 digits, from available_filters.industries), e.g. 25000000000 for Games.
objective string Campaign objectives, comma-separated: traffic, app_installs, conversions, video_views, reach, lead_generation, product_sales, app_promotion.
ad_language string Ad language codes, comma-separated, e.g. en or es,pt.
likes top_1_20 | top_21_40 | top_41_60 | top_61_80 | top_81_100 Likes percentile band: top_1_20, top_21_40, top_41_60, top_61_80, top_81_100.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/tiktok/v1/ad-library/top-ads?country=US" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.