Skip to content

Advertiser Search

GET/v1/google/adLibrary/advertisers/search1 credit

Searches the Google Ads Transparency Center for advertisers by name and returns the matching advertisers (name, id, region, estimated ad count) and matching website domains.

01Query parameters

NameTypeDescription
queryrequiredstringAdvertiser name to search for, e.g. `lululemon`.
regionoptionalstringTwo-letter country code, e.g. `US` or `AU`; `anywhere` or no value means every region.

02Request

curl "https://api.scrapesocial.ai/v1/google/adLibrary/advertisers/search?query=lululemon" \
  -H "x-api-key: $SCRAPESOCIAL_KEY"

03Responses

Real answers from the API. Lists are shortened to 2 items.

GET /v1/google/adLibrary/advertisers/search?query=lululemon

{
  "success": true,
  "credits_remaining": 4980,
  "credits_charged": 1,
  "advertisers": [
    {
      "name": "LULULEMON MEXICO",
      "advertiser_id": "AR02903092099014459393",
      "region": "MX",
      "number_of_ads_estimate": 16
    },
    {
      "name": "lululemon HK Limited",
      "advertiser_id": "AR01382517811867287553",
      "region": "HK",
      "number_of_ads_estimate": 5000
    }
  ],
  "websites": [
    {
      "domain": "lululemon.de"
    },
    {
      "domain": "lululemon.es"
    }
  ]
}

Common to every endpoint

Any route can answer these: a missing or wrong key, no credits left, the platform not answering, or a failure on our side. None of them costs credits.

GET /v1/cosmos/profile?handle=design

{
  "success": false,
  "message": "Invalid API key"
}

04Notes

Advertisers are in `advertisers` and domains in `websites`; there is no paging. Use an `advertiser_id` from here with the Company Ads route. A search that finds nothing is a 200 for 0 credits.

05Errors & credits

Every error has success: false, a real HTTP status and costs no credits.

  • 400missing_parameter

    A required parameter is missing or invalid.

  • 403private_account

    The account is private or age-restricted.

  • 404not_found

    No such account.

  • 503upstream_error

    The platform did not answer; retry shortly.