Enrich a CRM automatically from the company number
A company number is enough to fill in a client or prospect record properly: official name, registered office address, activities and published contact details.
The problem#
In a CRM the same company often exists three times: “Dupont SRL”, “DUPONT” and “Dupont & fils”, each with a slightly different address. Records are typed by hand, call after call, and nobody knows which one is right. Reports by sector or region become wrong, and invoicing picks the most recent address, not necessarily the correct one.
The company number is the stable identifier of a Belgian company. If your tool starts from that number, it can fetch the rest from the official source instead of asking someone to type it.
The API data that answers it#
GET /denominations?q=…: autocomplete on company names, to suggest the right company from the first letters typed and get its number.GET /enterprise/{num}: the main record (name, legal form, status, start date, registered office).GET /enterprise/{num}/address: the registered office address alone, if you only want to refresh that field.GET /enterprise/{num}/activities: every declared NACE activity, to classify your accounts by sector.GET /enterprise/{num}/denominations: every name (official, abbreviated, commercial) in the published languages.GET /enterprise/{num}/contact: phone, email and website, when the company published them.GET /naces: search in the NACE classification, to show the label of a code or build your own segments.
Example request#
"tok-comment"># 1. Type-ahead on the company name, returns enterprise numbers
curl "https://companybelgium.be/api/v2/denominations?q=espero&limit=5" \
-H "X-API-Key: $API_BCE_KEY" -H "X-API-Secret: $API_BCE_SECRET"
"tok-comment">
# 2. Once a number is chosen, read the record and its sub-resources
curl https://companybelgium.be/api/v2/enterprise/1033.022.383 \
-H "X-API-Key: $API_BCE_KEY" -H "X-API-Secret: $API_BCE_SECRET"
curl https://companybelgium.be/api/v2/enterprise/1033.022.383/activities \
-H "X-API-Key: $API_BCE_KEY" -H "X-API-Secret: $API_BCE_SECRET"
curl https://companybelgium.be/api/v2/enterprise/1033.022.383/contact \
-H "X-API-Key: $API_BCE_KEY" -H "X-API-Secret: $API_BCE_SECRET"The first call serves the entry screen: the user types a few letters, picks the right company, and your tool keeps its number. The following calls fill in the record from that number.
Recommended implementation#
- Make the company number the matching key of your accounts: two records with the same number are the same company.
- Do not silently replace an address typed by a sales rep: suggest the official value and let the user confirm.
- Store the date of the last enrichment and refresh active accounts periodically rather than the whole file every time.
- Call the sub-resources in parallel: they are independent of each other and each returns the standard JSON envelope.
- Put the call in your backend or in a scheduled job, never in the browser.
Limits to know#
- Contact details (phone, email, website) are only returned if the company published them; many publish none.
- With an application OAuth token, the contact endpoint requires the
enterprise:contactscope. A regular API key has access without a scope. - NACE activities are the ones declared to the register: they describe the purpose of the company, not necessarily what it actually sells today.
- The API does not return a sales contact person or named individuals to reach: it is not a prospecting database.
- Each call counts against your monthly quota: a bulk enrichment is planned according to your plan and the hourly limit.
Frequently asked questions#
Can I find a company by its name rather than its number?
Yes. GET /denominations?q=… returns suggestions with the company number of each one; then call the record with that number.
Which language are the names in?
In the languages published in the register: French, Dutch, German or English depending on the company. GET /enterprise/{num}/denominations returns them all.
How do I keep records up to date after enrichment?
Refresh active accounts periodically, or subscribe them to a webhook to be told when their record changes in the register.
Put it into practice
Create a key in the developer portal, then follow the reference documentation for each endpoint mentioned.
Reference documentation