POST /api/ariregister/companies
Price: 10 credits
Get an Estonian business's full registry record from the e-Business Register by its 8-digit registry code: name, legal form and subtype, status, enterprise register code, LEI code, VAT number and start date, share capital, founding and registration dates, financial year period, e-invoice operator, address and contacts, the management board and supervisory board (name, personal identification code, country, role, start and end dates), shareholders (name, contribution, share type), beneficial owners (name, manner of control), areas of activity (EMTAK code and type), annual reports (year, period, revenue, profit, profit margin and report download URL), articles of association documents (effective date, status and download URL) and tax information (tax debt, state and workforce taxes, taxable turnover and number of employees).
Look up one Estonian company by its 8-digit registry code (e.g. '10060701'). Returns one item with reg_code, name, legal_form, subtype, status, enterprise_register_code, lei_code, vat_number, vat_start_date, capital, founded_date, registered_date, financial_year_period, articles_amended_date, einvoice_operator, address, email, phone, website, board, supervisory_board, shareholders, beneficial_owners, activities, annual_reports, articles_of_association and tax. To find a registry code by company name, use ariregister/companies/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)reg_code string required — Estonian e-Business Register registry code (8 digits) (examples: "10060701")@type string (default: "AriregisterCompany")reg_code string requiredname string nullablelegal_form string nullablesubtype string nullablestatus string nullableenterprise_register_code string nullablelei_code string nullablevat_number string nullablevat_start_date string nullablecapital string nullablefounded_date string nullableregistered_date string nullablefinancial_year_period string nullablearticles_amended_date string nullableeinvoice_operator string nullableaddress string nullableemail string nullablephone string nullablewebsite string nullableboard array (default: [])@type string (default: "AriregisterPerson")name string requiredpersonal_id string nullablecountry string nullablerole string nullablestart_date string nullableend_date string nullablesupervisory_board array (default: [])@type string (default: "AriregisterPerson")name string requiredpersonal_id string nullablecountry string nullablerole string nullablestart_date string nullableend_date string nullableshareholders array (default: [])@type string (default: "AriregisterShareholder")name string requiredpersonal_id string nullablecountry string nullablecontribution string nullableshare_type string nullablestart_date string nullablebeneficial_owners array (default: [])@type string (default: "AriregisterBeneficialOwner")name string requiredpersonal_id string nullablecountry string nullablecontrol string nullablestart_date string nullableactivities array (default: [])@type string (default: "AriregisterActivity")name string requiredemtak_code string nullabletype string nullableannual_reports array (default: [])@type string (default: "AriregisterAnnualReport")year integer requiredsubmitted_date string nullableperiod string nullablestatus string nullablerevenue integer nullableprofit integer nullableprofit_margin string nullablereport_url string nullablearticles_of_association array (default: [])@type string (default: "AriregisterStatuteDocument")effective_date string nullablevalid_until string nullableapproval_date string nullablestatus string nullabledocument_url string nullabletax object nullable@type string (default: "AriregisterTaxInfo")has_tax_debt boolean nullabletax_debt string nullablestate_taxes string nullableworkforce_taxes string nullabletaxable_turnover string nullableemployee_count integer nullableperiod string nullableurl string required422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — No company found for the given registry code Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.