ContactPit

Data API · access on request

ContactPit API

Every Estonian and Latvian company, inside your product.

2national registers: Estonia and Latvia
1permanent company ID across every product
Everyfact comes with a source and a date

What do you want to do?

Your server

ContactPit

Data API

Ask. Get. Stay fresh.

  1. AskSend a registry code, name, website or filter.
  2. GetThe company, with a source and date on every fact.
  3. Stay freshThe change feed tells you what changed.

Base data

What is in the Data API

Company recordsEvery key
Search and matchingEvery key
Change feedEvery key
People and rolesBy agreement
FinancialsBy agreement
Tax, VAT and filingsBy agreement

Personal ID codes are never returned.

Getting access

One short call, then your key

  1. 1Tell us what you buildCountries, data and volume.
  2. 2Agree the termsDatasets, limits and use.
  3. 3Get your keyThen follow the docs.

There is no self-serve sign-up. Our team issues each key.

Intelligence · add-on

What the registry does not tell you

What a company sells, who it works with and where it is heading. Added to your key, under the same company ID.

Example Demonstration OÜ00123456 · EE
Status
Active
Activity
EMTAK 62011
Employees
4.5
Board
2 members
Data API
  • Products and servicesFrom the company website
    By agreement
  • Customers, partners and sponsorsNamed on the company website
    Pilot
  • Expansion and acquisition signalsFrom annual reports
    Pilot
  • Registry eventsLiquidation, merger, capital and VAT changes
    By agreement
  • Business contactsUnder a data-use agreement
    On request

Who uses it, and how

For products that work with Baltic companies

Estonian and Latvian company data, in the tools your customers already use.

  • CRM and SaaS teams

    The problem
    Company records are typed by hand and go stale.
    How they use it
    Match by registry code, name or website. The change feed keeps each record current.
  • Fintech, credit and KYB

    The problem
    Checking a new customer means visiting many registers.
    How they use it
    Read status from one source. Add VAT, filings, owners and board by agreement.
  • Lead generation and sales tools

    The problem
    Data on Estonia and Latvia is thin in global databases.
    How they use it
    Search by status, activity and staff count. Send the lists straight into your product.
  • Data teams

    The problem
    Rebuilding a register copy again and again.
    How they use it
    Keep your own copy. Read only what changed, in order.

What it solves

Clean data that stays clean

  • Copying company data by handOne clean format for two registers
  • Records that drift out of dateA change feed with every update
  • Facts you cannot traceA source and a date on every fact

Ready to build?

Tell us what you need and we will set up a key for it.