How do I match messy CRM company names to an official registry record?

Send up to 100 account names per call to POST /companies/lookup. Each fuzzy name match returns the best candidate with a match_score from 0 to 100; an exact company_number, nif, siren or vat resolves directly with no score needed.

What should I store as the dedupe key instead of the company name?

Country plus company_number — the identifier the registry itself assigns: NIF for Spain, SIREN for France, the Companies House number for the UK, the CRO number for Ireland, KRS for Poland, the organisation number for Norway. Validate the check digit first with the free company identifier validator.

How many CRM accounts can I resolve in one request?

Up to 100 items per POST /companies/lookup call. Each item still counts as one request against your monthly quota, so 50,000 accounts is 500 batch calls but 50,000 counted requests.

Does Prometiam return emails or phone numbers for CRM contacts?

No. Prometiam returns no personal emails and no inferred contacts — what comes back is registry data about the company itself: name, status, address, activity and, where published, officers. It is not a contact-finder product.

How do I keep enriched CRM records up to date?

Subscribe Spanish, Irish or Polish companies to POST /monitor for a webhook on status changes, dissolution and sanctions matches. For France, the UK and Norway, re-run the batch lookup for changed accounts on a schedule — nightly is typical.

CRM Company Data Enrichment API — Entity Resolution by Registry ID

A CRM account table built from imports, manual entry and old spreadsheets ends up with several spellings of the same company and no way to tell they are one account. Prometiam resolves a messy name or a partial identifier to the official registry record for Spain, France, the UK, Ireland, Poland and Norway, so RevOps, data and finance teams can key every account on one stable value: country plus the registry's own company number.

The pattern

Send up to 100 account names or partial identifiers per call to POST /companies/lookup. A name match comes back with a match_score from 0 to 100; an exact company_number, nif, siren or vat match resolves directly with no score needed. Store country plus company_number as the dedupe key — validate its check digit first with the free company identifier validator (Spain, France, Poland and Norway carry a real check digit; UK and Irish numbers do not) — then read legal_form, status, founding_date, dissolution_date, address, activity_code, activity_description, capital_amount, capital_currency and previous_names straight off the same result, or call GET /companies/{id} for the fuller profile. Validate a VAT number separately against VIES with GET /vat/{vatNumber}. Refresh Spanish, Irish and Polish accounts on a webhook with POST /monitor; refresh the other three countries by re-running the batch lookup on a schedule.

Honest limits

A fuzzy name match is a best guess with a score, not a certainty — keep anything below the threshold you choose on a review queue rather than writing it back automatically. Prometiam returns no personal emails, no inferred contacts, no financials, no employee counts and no credit score of any kind: only what the registry itself publishes about the company. Ireland and Poland are company-level with no officers yet; Norway has no corporate-event stream; former names are populated for the UK and Norway, not consistently elsewhere.

A 50,000-account CRM is 50,000 counted requests (500 batch calls of 100) — a one-off backfill that fits the Professional tier; a nightly refresh of only the accounts that changed fits Starter for most books.

What comes back

Field	What it is
`company_number` (+ `nif` / `siren`)	The registry primary key — the value to store as your dedupe key, alongside `country`.
`company_name`	Registered legal name, always uppercase.
`legal_form`	e.g. S.A., SARL, Ltd — null where the registry does not publish one.
`status`	Registry status in that country's own vocabulary (active, dissolved, in_liquidation, bankrupt…). Values are not a shared enum across countries.
`founding_date` / `dissolution_date`	Incorporation date and, where it applies, the date the entity closed.
`address`, `postal_code`, `city`, `province`	Registered address, uppercase.
`activity_code` / `activity_description`	CNAE (ES), NAF (FR), SIC (GB/IE), PKD (PL), NACE (NO). The description is text only for ES/FR/NO.
`capital_amount` / `capital_currency`	Share capital as last published, in the registry's own currency (EUR for ES/FR, PLN for PL, NOK for NO).
`previous_names`	Former registered names — sourced for the UK and Norway; the other four countries typically return none.
`last_seen_date`	The most recent registry publication in which Prometiam has seen this record.

Frequently asked questions

How do I match messy CRM company names to an official registry record?: Send up to 100 account names per call to POST /companies/lookup. Each fuzzy name match returns the best candidate with a match_score from 0 to 100; an exact company_number, nif, siren or vat resolves directly with no score needed.
What should I store as the dedupe key instead of the company name?: Country plus company_number — the identifier the registry itself assigns: NIF for Spain, SIREN for France, the Companies House number for the UK, the CRO number for Ireland, KRS for Poland, the organisation number for Norway. Validate the check digit first with the free company identifier validator.
How many CRM accounts can I resolve in one request?: Up to 100 items per POST /companies/lookup call. Each item still counts as one request against your monthly quota, so 50,000 accounts is 500 batch calls but 50,000 counted requests.
Does Prometiam return emails or phone numbers for CRM contacts?: No. Prometiam returns no personal emails and no inferred contacts — what comes back is registry data about the company itself: name, status, address, activity and, where published, officers. It is not a contact-finder product.
How do I keep enriched CRM records up to date?: Subscribe Spanish, Irish or Polish companies to POST /monitor for a webhook on status changes, dissolution and sanctions matches. For France, the UK and Norway, re-run the batch lookup for changed accounts on a schedule — nightly is typical.