Company Enrichment API
Send a company URL or public identifier and get firmographics back: industry, employee count and range, headquarters, founding year, website, domain, specialities and follower count.
These are the fields that decide territory assignment, lead routing and pricing tier, so they are worth having right rather than inferred.
- requests served per month
- 40M+requests served per month
- uptime
- 99.9%uptime
- median response time
- 1smedian response time
- serving production traffic since
- 2023serving production traffic since
What you send, what you get
A public company URL, a public identifier, or a numeric company ID.
- Identity
- name, companyId, publicIdentifier, url, tagline, description, logoUrl
- Firmographics
- industry, industryV1, employeeCount, employeeCountRange, foundedOn, specialities
- Location
- headquarter (line1, city, geographicArea, postalCode, country), locations
- Reach
- websiteUrl, domain, phone, followerCount
GET /api/v1/company. Full field reference in the documentation.
One call, start to finish
Request
curl "https://api.fetchin.io/api/v1/company?url=https://www.linkedin.com/company/microsoft" \
-H "X-API-Key: your-api-key"Response
{
"company": {
"name": "Microsoft",
"companyId": "1035",
"domain": "microsoft.com",
"websiteUrl": "https://news.microsoft.com/",
"industry": "Software Development",
"employeeCount": 238000,
"employeeCountRange": { "start": 10001 },
"foundedOn": { "year": 1975 },
"headquarter": {
"city": "Redmond",
"geographicArea": "Washington",
"country": "US"
},
"followerCount": 24000000,
"specialities": [ ... ]
}
}What teams build with it
Lead routing and territory
Assign an inbound account to the right rep the moment it arrives, using real headcount and headquarters rather than a self-reported company size field.
ICP scoring
Filter a pipeline on industry, size band and geography, so the accounts that reach a human are the ones worth a human.
Pricing and packaging
Tier a self-serve signup by employee count at the point of signup, instead of discovering the company size on the first invoice dispute.
Market research
Size a segment by pulling firmographics across a list of companies and grouping on industry, headcount range and founding year.
Why this endpoint
- Live firmographics, not a snapshot that drifts as companies hire and move
- Both the current industry taxonomy and the legacy industryV1 value, so existing mappings keep working
- Headcount as an exact number and as a range, so you can filter either way
- Domain and website resolved in the same call, which is usually the join key back into your CRM
- Accepts a URL, a public identifier or a numeric ID, so you do not have to normalise your inputs first
Walkthroughs that use it
Each of these takes one job end to end, with the flow and the code.
Questions
- What is company enrichment?
- Company enrichment fills a thin account record out with firmographics: what the company does, how many people work there, where it is based, when it was founded and how to reach it. It is what turns a company name in a CRM into something you can route, score and price against.
- Can I enrich from a domain?
- You can pass a company URL, a public identifier or a numeric company ID. The response includes the domain and website, which is normally the field you join back on, so a domain-first workflow is a lookup on your side followed by one call here.
- How accurate is the employee count?
- It is the count published by the company itself, read at the moment you call, and it is returned both as an exact number and as a band. It moves as the company hires, which is exactly why it is worth re-reading rather than storing once.
- What does a company lookup cost?
- One company call is one credit, on the same meter as every other endpoint, from $1.00 per 1,000. Failed requests are not billed, and 1,000 free credits are available with no card.
The rest of the API
Try it on your own data
1,000 free credits, no card. Failed requests are never billed, so a test that does not work costs nothing.