/snapchat/ads/search

POST /api/snapchat/ads/search

Price: 20 credits

Search Snapchat Political Ads Library archive by advertiser, candidate or committee name

How to use it

Search the Snapchat Political Ads Library archive for a given year. Filter by advertiser/organization/candidate/committee name (query) and/or targeted country. Returns id, creative_url, currency, spend, impressions, started_at, ended_at, advertiser and committee details, and full targeting (gender, age, country, regions, metros, interests, segments).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• year string required — Archive year of the political ads dump to search (one of: "2018", "2019", "2020", "2021", "2022", "2023", "2024", "2025", "2026")
• query string — Filter by advertiser, organization, candidate or committee name (case-insensitive substring) (default: ""; examples: "biden", "act party")
• organization_name string — Filter by organization name (case-insensitive substring) (default: ""; examples: "snap")
• paying_advertiser_name string — Filter by paying advertiser name (case-insensitive substring) (default: ""; examples: "biden for president")
• country string — Filter by targeted country name (case-insensitive substring, e.g. 'united states') (default: ""; examples: "united states", "canada")
• gender string nullable — Filter by the ad's gender targeting (one of: "MALE", "FEMALE")
• age_bracket string — Filter by the ad's exact age targeting range (open-ended set of advertiser-chosen ranges) (default: ""; examples: "18+", "18-35", "21+")
• count integer required — Max result count (examples: 20; min: 1)

Response

• @type string (default: "SnapchatAd")
• id string required
• year string required
• creative_url string nullable
• currency string nullable
• spend integer nullable
• impressions integer nullable
• started_at integer nullable
• ended_at integer nullable
• organization_name string nullable
• billing_address string nullable
• candidate_ballot_information string nullable
• paying_advertiser_name string nullable
• committee_name string nullable
• committee_id string nullable
• disclosure_name_of_committee string nullable
• advertising_jurisdiction string nullable
• gender string nullable
• age_bracket string nullable
• country string nullable
• regions_included array (default: [])
• regions_excluded array (default: [])
• electoral_districts_included array (default: [])
• electoral_districts_excluded array (default: [])
• radius_targeting_included array (default: [])
• radius_targeting_excluded array (default: [])
• metros_included array (default: [])
• metros_excluded array (default: [])
• postal_codes_included array (default: [])
• postal_codes_excluded array (default: [])
• location_categories_included array (default: [])
• location_categories_excluded array (default: [])
• interests array (default: [])
• segments array (default: [])
• os_type string nullable
• language string nullable
• advanced_demographics string nullable
• targeting_connection_type string nullable
• targeting_carrier string nullable
• creative_properties string nullable

Errors

• 422 — 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 — The entity was not found, or a precondition failed 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.