Skip to content
LeadityDocs

Account

Get analytics

Read what the account has swept and owns, per niche and state.

GETapi.leadity.io/v1/account/analytics
Scope readMCP tool get_analytics

Answers the account's lifetime footprint: for every niche it has scraped, per state, how many ZIP or postal codes were swept and how many leads it owns from there. A state can carry leads with no codes swept, because a search anchored on one code also returns its neighbours.

Headers

Authorizationstringrequired

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

Response

nichesobject[]required
Show child attributes
namestringrequired

The niche's name.

statesobject[]required
Show child attributes
countrystringrequired
statestringrequired
codesSweptintegerrequired

ZIP or postal codes swept for this niche in this state.

leadsOwnedintegerrequired

Delivered leads of this niche the account owns from this state.

Errors

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

CodeStatusMeaningExtra fields
unauthorized401The API key is missing, malformed, revoked or expired.-
wrong_key_kind401This key opens the other surface: an API key works on the HTTP API, an MCP key on the MCP server.-
account_suspended403The account is suspended.-
email_not_verified403The account's email address is not verified yet.-
rate_limited429Too 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_again503Leadity 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_error500Something 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.