Skip to main content
POST
Preview lead list count API

Frequently asked questions

It is a fast approximation designed to drive a live counter as someone adjusts filters, not an exact count. Billing always happens on the actual delivered row count, never on this number, so an overestimate never costs you anything.
Technology, keyword, country, industry and employee filters all move it. Among the website filters, has_email and has_phone apply coverage factors, while languages and web_countries are informational and do not move the estimate — they still filter the real build.
Yes, for 5 minutes per unique filter set, so a user toggling back and forth does not re-run the estimate each time.
One credit per row we would deliver. Cap it by setting list_size when you create the list — that is the maximum you can be charged.

Authorizations

Authorization
string
header
required

API key in format tapi_live_[32-char] (live) or tapi_test_[32-char] (test)

Body

application/json

The filter set that defines a lead list. Technology filters and company filters combine with AND.

technologies
object
keywords
object
website_type
string
Example:

"company_only"

countries
string[]
Example:
industries
string[]
Example:
employees
string[]
Example:
has_email
boolean

Only domains where the crawler found an email address.

has_phone
boolean

Only domains where the crawler found a phone number.

languages
string[]
Example:
web_countries
string[]

ISO-2 codes or English names. Unresolvable values are rejected at create time.

Example:

Response

Estimated match count and credit cost

success
boolean
Example:

true

data
object