Most of the questions people ask Fyonta's enrichment endpoints — "does this company exist," "how big are they," "where are they based" — don't need a live lookup at all. Fyonta owns a firmographic database of nearly 25 million companies, and /v1/leads/company-search queries it directly. It's a straight database read, not a proxied enrichment call, so it never touches your enrichment usage.
Why this is a separate endpoint from lead search
/v1/leads/search returns people — contacts with titles, seniority, and emails. /v1/leads/company-search returns companies — firmographic records with no people attached. If your first question is "which companies in this industry and size band are even worth prospecting," start here. Once you have a shortlist of companies, that's when you'd move to contact-level search or enrichment.
The filters that do the real narrowing
Five parameters cover almost every use case: q (fuzzy match on company name), domain (exact match), industry, region_code and country_code, and employee_count_range (bucketed, e.g. 1-10, 11-50, 51-200). A basic query for solar companies in Germany:
curl "https://api.fyonta.com/v1/leads/company-search?q=solar&country_code=Germany" \ -H "X-API-Key: $FYONTA_KEY"
Which returns records shaped like this:
{
"results": [{
"company_name": "1stop solar gmbh",
"domain": "1stopsolar.eu",
"industry": "information technology and services",
"employee_count_range": "11-50",
"city": "eschborn",
"region_code": "Hesse",
"country_code": "Germany",
"linkedin_url": "linkedin.com/company/1stop-solar-gmbh",
"founded": "2023"
}],
"count": 1,
"has_more": true,
"offset": 0,
"limit": 25
}
Combining filters for an actual target list
Stack the parameters to get an ICP-shaped list instead of a single lookup. IT services companies with 11–200 employees in California:
curl "https://api.fyonta.com/v1/leads/company-search?industry=IT+Services&employee_count_range=11-50,51-200®ion_code=CA" \ -H "X-API-Key: $FYONTA_KEY"
There's no minimum number of filters required — a bare q search works fine for a quick lookup — but stacking industry, size, and geography is what turns this into a usable account list rather than a single-record check.
Checking a specific domain before you enrich it
If you already have a list of domains from another source and want to confirm they're real, active companies with reasonable firmographic detail before spending enrichment credits on the people behind them, run each through domain:
curl "https://api.fyonta.com/v1/leads/company-search?domain=acme.com" \ -H "X-API-Key: $FYONTA_KEY"
This is a cheap sanity check to run before a batch enrichment job — filter out domains that don't resolve to a real company record first, rather than finding out after you've spent enrichment calls on them.
Pagination works the same as everywhere else
limit caps at 100 per request; use offset to page through a larger result set rather than trying to pull everything in one call. has_more in the response tells you whether there's another page waiting.
Where this fits with enrichment
Company search answers "who should I even be looking at." When you need the person — an email, a phone number, or a name behind a domain — that's when you'd reach for the enrichment endpoints like contact-finder or domain-search, documented on the docs page. Keeping the free, owned-database lookup separate from the live enrichment calls is deliberate: you shouldn't have to spend a credit just to find out if a company is worth pursuing.