CRM and database enrichment

A contact database starts ageing the moment it is created. Enrichment from the registers restores its accuracy and adds information the sales rep had no way of knowing at entry.

The problem

The CRM has a company ID, a name and maybe an address. Industry, size, legal form and the fact that the company has since been dissolved are all missing. The rep finds out on the call.

Segmentation on such data does not work. A campaign aimed at companies in a given industry cannot be built if the industry is nowhere to be found.

How FirmAPI solves it

Batch processing fills the entire existing database at once: NACE classification, legal form, date of establishment, registered address, status. Segments follow immediately.

After that it is enough to track changes. A webhook on a change of address, name or officer keeps the database accurate without anyone having to sweep it.

Dissolved entities can be flagged automatically. It is the cheapest way to remove from the database the contacts nothing can be sold to.

Enriching an existing record
GET /v1/company/ico/51636549?scope=all

{
  "data": {
    "name": "Version Two s. r. o.",
    "legal_form": "Limited liability company",
    "established_date": "2018-03-14",
    "terminated_date": null,
    "nace_code": "62.01",
    "nace_description": "Computer programming"
  }
}

Frequently asked questions

How do I enrich a database of tens of thousands of records?

Through batch processing. You upload a list of company IDs and collect the result when it is ready – no loop over the endpoint and no risk of hitting a limit.

Can companies be filtered by industry and region?

Yes, through search with filters. Combining a NACE code with a district is the usual way to build a target list.

Try it on your own data

A free account requires no payment card. Our database holds 2 160 466 entities from 48 public registers.

We respect your privacy

We use necessary cookies to make the site work. With your consent we also use analytics cookies (Google Analytics) to understand how the site is used. More in our Privacy Policy.