Overview
In Kyckr’s migration from the EBR (European Business Registry Network), we’ve updated Search, Lite Profile, and Enhanced Profile responses for Estonia (ISO code EE). Enhanced Profiles remain available and have been improved with better data quality and additional fields.Search results
We’ve improved the structure and data quality of Search responses for Estonia companies.Response structure changes
The search response structure has been updated for better consistency and additional company information. Before:Key changes
The following fields are now populated in search responses:- Address information:
addressInOneLineFieldis now populated with the full Estonian format address - Legal form:
legalFormFieldnow provides the company’s legal form (e.g., “Public limited company”) - Legal status:
legalStatusFieldnow provides the company’s legal status (e.g., “Entered into the register”) - Registration number:
registrationNumberFieldnow provides the company’s registration number - Registration date:
registrationDateFieldnow provides the company’s registration date in ISO format
registrationAuthorityCodeFieldis no longer includedlineField,cityTownField, and additional empty address fields have been removed
Lite profile changes
The response structure has been updated due to the new provider, with improved activity data, address parsing, and additional fields.Response structure changes
Before (V1 format):Field mapping changes
Activity data
Key improvements:- Activity codes (
codeField) are now populated - Multiple activities are now captured when available
Address structure
The address structure has been improved with better parsing and more populated fields: Key improvements:countryFieldis now populated (previously empty)cityTownField,regionStateField, andpostcodeFieldare now properly parsed and populated
Company identification
Key changes:registrationNumberFieldis now included, providing the registration number separately fromcodeFieldfoundationDateFieldis now populated with the company’s foundation dateregistrationDateFieldformat has been improved to ISO format (YYYY-MM-DD) instead of DD.MM.YYYY
Legal form and status
Key changes:- Status normalization now uses title case (
"Active") instead of uppercase ("ACTIVE")
Additional fields
New fields added:aliasesField: Array of company aliases (may be empty)otherIdentifiersField: Array of other company identifiers (may be empty)
Enhanced profile changes
The response structure has been updated due to the new provider, with improved data quality across multiple fields.Response structure changes
Before (V1 format):Field mapping changes
Activity data
Key improvements:- Activity descriptions (
descriptionField) are now populated alongside codes - Multiple activities are now captured when available
Address structure
The address structure has been improved with better parsing:addressInOneLineFieldnow uses Estonian format (region first)cityTownField,countryField,postcodeField, andregionStateFieldare now populatedtypeFieldnow uses standardized descriptions (e.g., “Registered Address” instead of “Business address”)
Directors and representatives
Key improvements:appointedOnFieldis now populated with appointment dates in ISO formatdirectorNumberFieldis now included for director identification
Shareholders
New fields added:shareHoldersFieldis now populated with share holdings and shareholder details- Includes shareholder identification (
idField), name (nameField), share percentage (percentageField), nominal value (nominalValueField), and shareholder type (shareholderTypeField- “Person” or “Company”)
Capital information
Key improvements:typeCodeFieldis now populated (e.g., “L” for Ordinary ownership)typeFieldnow uses standardized descriptions (e.g., “Ordinary ownership” instead of “Capital”)
Legal form and status
Key changes:legalFormFieldnow provides English translated legal form (e.g., “Public limited company” instead of “Aktsiaselts (AS)”)- Status normalization now uses title case (
"Active") instead of uppercase ("ACTIVE")
Identifiers
Key changes:vatNumberFieldis deprecated and no longer populatedotherIdentifiersFieldis now populated and captures VAT numbers where available (e.g.,{"typeField": "EE100154681", "valueField": "EE_VAT_CD"})- This provides a more structured approach to handling various identifier types