POST /api/spyfu/keywords/ad_history
Price: 20 credits
Get the advertisers and Google Ads seen on a keyword, with ad copy, dates and positions
Get the ad history of one keyword: every advertiser SpyFu saw bidding on it with the ads it ran (headline, text, landing URL, date, position), and the best-performing ads on the keyword.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string required — Keyword or SpyFu keyword URL (examples: "crm software", "https://www.spyfu.com/keyword/overview?query=crm+software"; minLength: 1)country_code string — Search market (UK, not GB) (default: "US"; one of: "AR", "AT", "AU", "BE", "BR", "CA", "CH", "CL", "CZ", "DE", "DK", "ES", "FI", "FR", "IE", "IN", "IT", "JP", "MX", "NL", "NO", "NZ", "PL", "PT", "SE", "SG", "TR", "UA", "UK", "US", "VE", "ZA")@type string (default: "SpyfuKeywordAdHistory")keyword string requiredadvertiser_count integer nullableadvertisers array (default: [])@type string (default: "SpyfuKeywordAdvertiser")id string requireddomain string requiredad_budget number nullablecoverage number nullableleaderboard_share number nullableads_purchased_count integer nullablead_count integer nullableads array (default: [])@type string (default: "SpyfuAd")id string requireddate string nullableposition integer nullabletext string nullabledomain string nullableurl string nullablekeyword string nullablekeyword_id string nullablead_count integer nullableis_leaderboard boolean nullabletop_ads array (default: [])@type string (default: "SpyfuTopAd")id string requiredtext string nullableurl string nullableaverage_position number nullableaverage_ad_count number nullableleaderboard_count integer nullableleaderboard_share number nullableads_served_share number nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — SpyFu has no data for this keyword. Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.