Short answer
If your product handles Estonian or Latvian companies, you need three things: a clean record for each company, a way to match your own data to it, and a way to hear when it changes. The ContactPit Data API gives you all three for both countries in one format, with a source and a date on every fact.
The problem with doing it yourself
Estonia and Latvia each have their own register, with their own formats, field names and meanings. Building against both means two integrations, two sets of edge cases and a nightly job to notice what changed. Global databases cover both countries, but thinly: fields are missing, and updates arrive late.
So most products end up with company records typed in by hand. They are wrong on day one and stale by the end of the year.
What is in the Data API
Every key gets the core:
- Company records. Legal name, status, legal form, activity code, employees, website, city and region, with a source for every field.
- Search and matching. Exact match by registry code, candidates by name or website, and filtered search by status, activity and size.
- Change feed. Ordered updates, deletions and replacements, so your copy stays current.
The rest is switched on per key, once we agree how you will use it:
- Financials. Annual report history, the latest summary and revenue and profit headlines, as exact values with currency and period.
- People and roles. Board members and other officers, shareholders and beneficial owners, and the companies a company holds shares in.
- Tax, VAT and filings. VAT registration status, annual report years and the latest submitted report.
- Business profile. What a company does, in English and Estonian, read from its own website: summary, segments, markets, offerings, brands and certifications.
- Signals. Dated events such as liquidation, merger, name or capital change, licence, VAT, tax debt and headcount changes.
What teams build with it
- CRM and SaaS products stop asking users to type company details. They match by registry code, name or website, fill the record, and let the change feed keep it current.
- Fintech, credit and KYB teams read company status from one source instead of visiting several registers for each new customer, then add VAT, filings, owners and board by agreement.
- Lead generation and sales tools search by status, activity and staff count and send the lists straight into their product.
- Data teams keep their own copy and read only what changed, in order, instead of rebuilding a register copy again and again.
How an integration works
- Ask what your key can use. The capabilities call lists your scopes, registers and limits. Show a feature in your product only when it is on.
- Match your existing records. Send a registry code for an exact match. The code is matched as text, including leading zeros. A name or a website domain returns candidates with a reason, not confirmed matches.
- Store the ContactPit company ID. It is permanent and stays the same when a company changes its name or address.
- Search and page. Ask which filters a register supports, then search. Pages hold up to 50 companies.
- Follow the change feed. Keep the cursor from your search and poll for changes every few minutes.
Requests and responses are JSON over HTTPS. The key goes in the Authorization header and is used from your server only, never from a browser or a mobile app. The default limit is 120 requests a minute per customer. The full reference is in the API documentation.
Data principles worth checking in any provider
- A source and a date on every fact. You can show your users where a value came from and when it was observed.
- A missing value comes with a reason. Unknown is never turned into false, zero or an empty list.
- Identity by registry code. Names and websites only ever give candidates.
- Exact numbers. Financial amounts are exact decimal values with their currency and period. No conversion or growth maths is done for you.
- No personal ID codes. They are never returned.
Common mistakes
The first is matching by name. Two companies can share a name and one company can change it; the registry code is the only safe key. The second is copying the data once and never syncing, which recreates the stale-record problem inside your own database. The third is calling the API from the browser, which exposes the key.
Getting access
There is no self-serve sign-up. Access is set up by our team and usually takes one short conversation: tell us what you are building, which countries you need and roughly how many companies you will read. Construction projects and research lists are also available through the API for pilot partners; see Construction Radar and Market Scout.
FAQ
Is there an API for Estonian and Latvian company data?
Yes. The ContactPit Data API returns registered companies from the Estonian Business Register and the Latvian Enterprise Register in one JSON format, with a source and date on every fact.
How do I get an API key?
There is no self-serve sign-up. You tell us what you are building, which countries you need and roughly how many companies you will read. We agree the datasets, the request limit and how the data may be used, then send a server key.
Does the API return personal ID codes?
No. Personal ID codes are never returned. Role and ownership records name board members, officers, shareholders and beneficial owners without them.
How do I keep my copy of the data up to date?
With the change feed. After a search you poll the feed with a cursor and apply ordered updates, deletions and replacements. Polling every few minutes is plenty.