Catalog

List niches

List the niches you can order, grouped by market.

GETapi.leadity.io/v1/niches

Scope readMCP tool list_niches

Lists the niches Leadity sells, each one a Google Maps category, grouped by buyer market. Pass q to search by niche or group name instead of reading all of them. Use a niche's id in nicheIds when you call estimate_scrape and create_scrape.

Example request

curl "https://api.leadity.io/v1/niches?q=roof" \
  -H "Authorization: Bearer $LEADITY_API_KEY"

Example response

{
  "version": "3f9a1c2b7d4e",
  "groups": [
    {
      "group": "Home Services & Construction",
      "niches": [
        {
          "id": "roofing_contractor",
          "name": "Roofing Contractor",
          "multiplier": 1,
          "findOwner": true
        }
      ]
    }
  ]
}

Headers

Authorizationstringrequired

Bearer, a space, then an API key: Bearer lk_api_... An MCP key is refused here with wrong_key_kind.

Query parameters

qstring

Search text, matched against niche and group names.

1 to 100 characters.

Response

versionstringrequired

The catalog's content version. It changes whenever a niche or a price moves.

groupsobject[]required

Show child attributes

groupstringrequired

nichesobject[]required

Show child attributes

idstringrequired

The niche id, Google's own category slug, e.g. roofing_contractor.

namestringrequired

multipliernumberrequired

Multiplies the base price of a new lead in this niche.

findOwnerbooleanrequired

Whether the owner-name lookup may be ordered for this niche.

Errors

Every refusal answers { error, message } with the status below. The full list is on the Errors page.

Code	Status	Meaning	Extra fields
unauthorized	401	The API key is missing, malformed, revoked or expired.	-
wrong_key_kind	401	This key opens the other surface: an API key works on the HTTP API, an MCP key on the MCP server.	-
account_suspended	403	The account is suspended.	-
email_not_verified	403	The account's email address is not verified yet.	-
invalid_body	400	The request does not match the operation's schema.	`issues`: The problems found, each with path (the field as a dotted path, led by the part of the request it travels in: path, query or body, such as body.items.1) and message (what is wrong there).
rate_limited	429	Too many requests. Wait for the Retry-After seconds and try again.	`retryAfterSeconds`: The seconds to wait, the same number as the Retry-After header.
try_again	503	Leadity could not answer just now. Retry in a moment, with the same Idempotency-Key on a spending call.	`retryAfterSeconds`: When a request with this Idempotency-Key is still being processed: the seconds to wait before retrying with the same key, as the Retry-After header says.
internal_error	500	Something failed on our side. Nothing was charged twice.	`body`: On the MCP server, when Leadity answered in a shape the tool does not publish: that answer as it came.