LeadQuasar
Start free
BetaComing soon · Max plan

KeywordQuasar API

Keyword search volume for any city or country, with keyword ideas, cost per click, Bing and the businesses there to sell to, from your own code.

Request beta access Read the docs

A keyword search volume API with the businesses to sell to

What is the KeywordQuasar API?

The KeywordQuasar API is LeadQuasar’s keyword research API. Send a keyword and a place, and one request returns Google’s monthly searches there from Google Ads Keyword Planner data, keyword ideas with cost per click, Bing searches, a Google Trends link and the businesses there to sell to. It is in beta, and launches on Max.

The KeywordQuasar API at a glance

Status
Coming soon · Max plan · Beta
Endpoint
POST /api/v1/keyword-research
Authentication
A Bearer key, issued by LeadQuasar during the beta
Where
Any city, county, state or country Google Ads can target
Businesses to sell to
LeadQuasar's database of 9.7 million+ records

What the API returns

One request, one report: the same report as the KeywordQuasar tool on Max, as JSON. Every figure is its source’s own, not adjusted by LeadQuasar.

What a KeywordQuasar API report holds, and the source of each part
PartSource
Monthly Google searches for the keyword in the placeGoogle Ads Keyword Planner
Cost per click (top of page, low to high) and competitionGoogle Ads Keyword Planner
Keyword ideas, up to 500, each with searches, competition and bidsGoogle Ads Keyword Planner
Bing searches over four weeks, the "keyword + city" phrase, related keywordsBing Webmaster Tools
Businesses of that kind in the place, with no website, with an emailLeadQuasar's business database
Best cities for the niche, up to 50LeadQuasar's business database
A link to the lead listLeadQuasar
The past 12 months' chart: a link and Google's official embedGoogle Trends

A sample request and response

Example: "plumber" in Austin, TX. The place and Google's figures are Google's own answer, measured 30 Oct 2026; Bing, business and usage values change daily, so they are shown as their types.

POST /api/v1/keyword-research
{
  "keyword": "plumber",
  "location": "Austin, TX",
  "country": "US"
}
200 OK
{
  "data": {
    "keyword": "plumber",
    "location": {
      "name": "Austin",
      "city": "Austin",
      "state": "Texas",
      "country": "US",
      "geoId": "1026201",
      "targetType": "City"
    },
    "language": "en",
    "google": {
      "status": "ok",
      "currency": "USD",
      "main": {
        "keyword": "plumber",
        "searches": 3600,
        "competition": "LOW",
        "bidLow": 33.09,
        "bidHigh": 113.13
      },
      "ideas": [
        {
          "keyword": "emergency plumber",
          "searches": 480,
          "competition": "LOW",
          "bidLow": 52.29,
          "bidHigh": 178.5
        },
        <more ideas, up to 500 in all>
      ]
    },
    "bing": {
      "volume30d": <integer | null>,
      "cityPhrase30d": <integer | null>,
      "related": [
        <string>,
        <…>
      ]
    },
    "businesses": {
      "total": <integer>,
      "capped": <boolean>,
      "noWebsite": <integer | null>,
      "withEmail": <integer | null>,
      "scope": "city",
      "scopeName": "Austin"
    },
    "notCovered": false,
    "bestCities": [
      {
        "city": <string>,
        "state": <string | null>,
        "businesses": <integer>
      },
      <up to 50 cities>
    ],
    "bestCitiesCapped": <boolean>,
    "leadListUrl": <URL | null>,
    "trends": {
      "exploreUrl": "https://trends.google.com/trends/explore?date=today+12-m&geo=US-TX&q=plumber",
      "embedUrl": "https://trends.google.com/trends/embed/explore/TIMESERIES?req=%7B%22comparisonItem%22%3A%5B%7B%22keyword%22%3A%22plumber%22%2C%22geo%22%3A%22US-TX%22%2C%22time%22%3A%22today%2012-m%22%7D%5D%2C%22category%22%3A0%2C%22property%22%3A%22%22%7D&tz=0&eq=q%3Dplumber%26geo%3DUS-TX%26date%3Dtoday%2012-m"
    },
    "generatedAt": <ISO 8601 time>
  },
  "usage": {
    "usedToday": <integer>,
    "limitToday": <integer>
  },
  "meta": {
    "apiVersion": "v1",
    "source": "Google Ads Keyword Planner, Bing Webmaster Tools, LeadQuasar business data"
  }
}

Use cases for each data source

Four sources in one answer. What each one is for, and the part of the response it fills.

Bing Webmaster Tools

Bing searches and related keywords

Bing's own count of searches for the keyword over the last four weeks, country-wide, the searches for the keyword typed with the city, and Bing's related keywords.

  • Size the second search engine: Bing's results also feed Microsoft Copilot and some of ChatGPT's web search.
  • See how often people type the city into the search ("plumber austin"), a direct sign of local intent.
  • Find wording Google's ideas miss in Bing's related keywords.

Bing's values change weekly, so they are shown as their types.

Request
{
  "keyword": "plumber",
  "location": "Austin, TX",
  "country": "US"
}
Response (the part it fills)
{
  "data": {
    "bing": {
      "volume30d": <integer | null>,
      "cityPhrase30d": <integer | null>,
      "related": [
        <string>,
        <…>
      ]
    }
  }
}

LeadQuasar's business data

Who to sell to

How many businesses of that kind LeadQuasar holds in the place, how many have no website and how many have an email, the best cities for the niche, and the lead list one link away.

  • Turn demand into a prospect list: the businesses in the city that the searches are for.
  • Spot the easy pitch: businesses with no website where people search every month.
  • Pick where to expand: up to 50 cities with the most of these businesses in the country.

Business counts change daily as LeadQuasar adds businesses, so they are shown as their types.

Request
{
  "keyword": "plumber",
  "location": "Austin, TX",
  "country": "US"
}
Response (the part it fills)
{
  "data": {
    "businesses": {
      "total": <integer>,
      "capped": <boolean>,
      "noWebsite": <integer | null>,
      "withEmail": <integer | null>,
      "scope": "city",
      "scopeName": "Austin"
    },
    "bestCities": [
      {
        "city": <string>,
        "state": <string | null>,
        "businesses": <integer>
      },
      <up to 50 cities>
    ],
    "leadListUrl": <URL | null>
  }
}

Combined workflows

The sources together answer what no single one does: where there is demand, and who there to sell to. Each example calls lookup(), the small helper in the docs.

SEO and web agencies choosing where to sell next

Agency city and niche finder

  1. Call the API for one niche in each city on your shortlist.
  2. Rank the cities by monthly searches and cost per click (google.main), against the businesses there (businesses.total and noWebsite).
  3. Open the lead list (leadListUrl) for the city that comes out on top.
const cities = ["Austin, TX", "Dallas, TX", "Houston, TX"];
const rows = [];
for (const location of cities) {
  const { data } = await lookup({ keyword: "roofer", location, country: "US" });
  rows.push({
    location,
    searches: data.google.main?.searches ?? 0,
    bidHigh: data.google.main?.bidHigh ?? 0,
    businesses: data.businesses?.total ?? 0,
    noWebsite: data.businesses?.noWebsite ?? 0,
  });
}
rows.sort((a, b) => b.searches * b.bidHigh - a.searches * a.bidHigh);

Agencies reporting to local clients

Monthly client market report

  1. Once a month, look up each client's main keywords in their city.
  2. Store Google's searches and bids, Bing's four-week count and the Trends link beside last month's.
  3. Send the change, with the Trends chart embedded (trends.embedUrl).
for (const client of clients) {
  for (const keyword of client.keywords) {
    const { data } = await lookup({ keyword, location: client.city, country: client.country });
    await saveRow({
      client: client.id, keyword, month: new Date().toISOString().slice(0, 7),
      searches: data.google.main?.searches ?? null,
      bidHigh: data.google.main?.bidHigh ?? null,
      bing: data.bing?.volume30d ?? null,
      trends: data.trends.embedUrl,
    });
  }
}

Teams that sell to local businesses

Lead-gen pipeline

  1. Find a niche and city with demand (google.main) and businesses without websites (businesses.noWebsite).
  2. Open leadListUrl in LeadQuasar and save the list.
  3. Read the saved list and add it to your CRM with the account API (GET /api/v1/lists/{id}/leads, POST /api/v1/crm).
const { data } = await lookup({ keyword: "dentist", location: "Phoenix, AZ", country: "US" });
if ((data.google.main?.searches ?? 0) > 0 && (data.businesses?.noWebsite ?? 0) > 0) {
  console.log("Open and save:", data.leadListUrl);
}
// Later, with an account API key: GET /api/v1/lists/{id}/leads, then POST /api/v1/crm.

Limits

Read from the same settings the API enforces.

KeywordQuasar API limits
Lookups a daySet per key when it is issued: 100 unless agreed otherwise, and at most 300 during the beta. One successful report is one lookup, and the day resets at 00:00 UTC. When it is spent: 429 rate_limited, with Retry-After.
Calls per key60 a minute and 5,000 a day, whatever the endpoint. Past either: 429 rate_limited, with Retry-After; the message says which and when it resets (the next minute, or 00:00 UTC).
Place searches a dayEvery lookup uses one, and so does every call to the locations endpoint; the two share the key's day: three per lookup in its day, at most 300 (300 for a key with the default 100 lookups). A place search never uses up a lookup. When they are spent: 429 rate_limited until 00:00 UTC, with Retry-After.
Invalid keysAfter 30 requests with a missing or unknown key from one address in 10 minutes, that address is refused (429 rate_limited, Retry-After) for up to 10 minutes, even with a valid key. A paused, revoked or expired key does not count.
Not chargedEvery error: invalid requests, unknown or ambiguous places, refused keys, 500, and 503 when Google is busy or down (which carries no data and no usage).
Repeat lookupsGoogle and Bing answers are kept 30 days and shared, so a repeat is fast. It still counts as a lookup.
Request bodyUp to 4,096 bytes of JSON. A larger body is answered 400 invalid_request.
Keyword2 to 80 characters
LocationUp to 120 characters
Keyword ideas per reportUp to 500
Best cities per reportUp to 50
Places offered when a name is ambiguousUp to 8
Where to call fromYour server. CORS is off, and a key in a web page is a key anyone can use.

LeadQuasar also has an account API on Max, for your saved lists, leads and CRM: the REST API.

KeywordQuasar API questions

What is a keyword search volume API?

An API that answers how many people search for a keyword each month. The KeywordQuasar API gives Google's figure for the exact city, region or country you name, from Google Ads Keyword Planner data, with keyword ideas, cost per click and competition, Bing searches, and the businesses there to sell to.

Who can use the KeywordQuasar API?

It is in beta. LeadQuasar issues keys by hand to a LeadQuasar account, free or paid, on request; there is no self-serve key yet. When it launches it will be part of the Max plan ($29.99/month).

How are lookups counted?

One successful report is one lookup against the key's daily limit, which resets at 00:00 UTC. A repeat of a recent lookup is served from a shared cache and still counts. Invalid requests, unknown or ambiguous places, and answers while Google is busy or down are not charged.

Where do the numbers come from?

Searches, cost per click, competition and keyword ideas are Google Ads Keyword Planner data, asked for the place and language you send. Bing figures are Bing Webmaster data. The businesses are counted from LeadQuasar's database of 9.7 million+ records. Every figure is its source's own, not adjusted or rounded up by LeadQuasar.

Does it work for any city or country?

Search numbers work for any place Google Ads can target, from a city to a whole country, asked in the place's main language unless you send one of Google's 51 others. Business counts cover the countries in LeadQuasar's database; elsewhere the answer says so (notCovered).

Can I call it from a web page?

No. CORS is off and the key must stay secret, so call it from your own server, a script or a workflow tool, and pass the results on to your front end.

Does it give keyword difficulty or backlinks?

No. It answers how many people search for a keyword in a place, what a click costs and who there to sell to. Keyword difficulty, backlinks and ranking history are what full SEO suites such as Semrush and Ahrefs are for.

Will it return Google Trends numbers?

Today each report carries a link to the keyword's Google Trends chart and Google's official embed of it. The numbers themselves will be added when Google approves LeadQuasar's Trends API access.

Is this the same as LeadQuasar's API for lists and the CRM?

No. That is the account API, on Max: it reads your saved lists and leads and reads and writes your CRM, with keys you make in Settings. A KeywordQuasar key is issued separately during the beta.

Related

Get early access

During the beta, keys are issued by hand to a LeadQuasar account, free or paid. Tell us what you will build and the email of your account. At launch the API is part of Max.

Request beta access Read the docs