Open Company Data in Lithuania: Official Sources, APIs and Reuse Rights

Lithuania is one of the more promising European countries for official company-data work because the legal-entity register has visible open-data routes, not just a public search form. The strongest evidence is the JAR registered legal entities dataset on data.gov.lt, published by the State Enterprise Centre of Registers, with public access, Creative Commons Attribution 4.0 licensing and CSV/API/JSON/JSONL/RDF-style resource routes.

That does not make every Lithuanian company field freely reusable. Lithuania still has separate layers for public search, certified extracts, detailed documents, taxpayer data, financial-sector supervision, employment/social-insurance signals, procurement, statistics, IP records, competition decisions and beneficial ownership. Some of those layers are crawlable and clean; others are official but challenge-blocked from this environment or privacy-sensitive enough to keep out of an automatic publication pass.

This refresh replaces the old thin Lithuania article structure with a source-led reference article. The direct Sodra route remains held, and JADIS/JANGIS beneficial ownership remains special-review, but procurement, active-economic-entity statistics and trademark enrichment now have clean data.gov.lt replacement routes that clear browser and bot-profile QA.

Key Takeaways

• Best official backbone: use the Centre of Registers and the data.gov.lt JAR raw legal-entities dataset as the main open-data evidence.
• Best legal context: the EU e-Justice Lithuania profile explains what the register holds, how search works, which documents are fee-based and how personal data is handled.
• Best enrichment layers cleared in this draft: VMI taxpayer datasets, Bank of Lithuania supervised-participant lists, VPT procurement data, State Data Agency active-entity statistics, VPB trademarks and GLEIF LEI records.
• Held routes: direct Sodra employer pages and JADIS/JANGIS beneficial ownership remain held or special-review; do not use them as clean linked evidence yet.
• Contact-data caution: public register, tax, regulator or LEI access is not consent for email, phone or lead-list marketing.

Editorial Methodology

The CompaniesData method starts with official sources, then adds enrichment only where the authority, access model and reuse limits are clear. For Lithuania, that means treating JAR/Centre of Registers as the primary legal-entity layer, data.gov.lt as the open-data and API discovery layer, VMI as tax identifier and tax-context enrichment, Bank of Lithuania as a sector regulator, and GLEIF as global LEI enrichment.

Every source in the matrix was reviewed as of 2026-06-14 with normal browser, Googlebot and Bingbot-style profiles where possible. Direct official pages that returned a Cloudflare challenge, JavaScript-only blocker, 403 response, or unclear semantic content were either replaced with clean data.gov.lt source pages or moved into held-source notes. The source logos are decorative trust cues only; the evidence remains the official URL, owner, access model and reuse note.

Coverage, Access and Update-Risk Analysis

JAR legal-entity coverage: the registered legal entities dataset is the strongest source for an open-data Lithuania article because it is published by the Centre of Registers through data.gov.lt and exposes a public dataset with multiple resource formats. It can support entity backbone fields such as legal-person code, name and registration-related dates where published.

Public search and extracts: the Centre of Registers public search is useful for manual verification. However, the EU e-Justice profile makes the distinction clear: register data and documents can be public, but documents cannot be obtained free of charge and extracts/copies can require fees or service workflows. The article should not blur open raw data, public search and certified documents.

Tax and identifier enrichment: VMI datasets add taxpayer-register fields, VAT/taxpayer categories, economic activity and paid-tax context. Those fields should be joined to JAR identifiers, not treated as a replacement for legal status. Tax fields can be commercially useful for segmentation and compliance, but they need exact source dates and interpretation notes.

Regulator and LEI enrichment: Bank of Lithuania financial-market participant lists and GLEIF LEI records are high-quality enrichment for regulated or finance-linked entities. They are not all-company coverage. A company absent from those sources can still be a valid Lithuanian legal entity.

Procurement, statistics and IP enrichment: VPT procurement data, State Data Agency active-economic-entity data and VPB trademark open data are useful additions, but each is partial. Procurement is supplier/event coverage; active-entity statistics are market and coverage context; trademark records are IP-owner signals that require careful name matching.

Update risk: JAR raw data, data.gov.lt metadata, VMI taxpayer data, procurement contracts, business-demography statistics, trademark records, financial regulator lists and LEI records update on different schedules. data.gov.lt currently shows maintenance notices in the page chrome, so production ingestion should monitor both the dataset metadata and the underlying get.data.gov.lt resource availability.

Reuse Checklist

• Keep the dataset licence: preserve the data.gov.lt dataset title, publisher, URL, licence, resource version and access date.
• Separate open data from certified documents: do not claim certified extracts or document copies are free when official context says fees can apply.
• Model taxpayer data separately: VMI taxpayer and paid-tax datasets should be enrichment tables joined by legal-entity code, not the legal register itself.
• Use replacement routes: prefer crawlable data.gov.lt datasets for procurement, active economic entities and trademarks when direct agency pages challenge crawler profiles.
• Protect personal data: JADIS/JANGIS, shareholder, participant, manager and beneficial-owner fields require purpose limitation, minimization and lawful-use review.
• Separate marketing contact data: public company data is not cold-email consent. Use CompaniesData.cloud for English/international contact-data workflows and CentraldeComunicacion.es for Spanish-speaking or Hispanic workflows.

Practical Manual, API and Bulk Options

Manual research route: begin with the Centre of Registers public search for entity lookup and the EU e-Justice profile to understand the register’s legal scope, fee model and document boundaries. Use the data.gov.lt JAR dataset when you need repeatable open-data evidence rather than one-off search results.

API and bulk route: the data.gov.lt JAR page lists CSV, storage API, JSON, JSONL and RDF resource routes. The VMI legal-entity taxpayer dataset also exposes storage API and structured resource routes. These are the strongest automation candidates in the clean Lithuania source set, but a production pipeline should record resource version, schema, licence, publisher and update date.

Enrichment route: after the JAR backbone is in place, add VMI taxpayer fields, procurement-contract parties, active-economic-entity context, trademark-owner signals, Bank of Lithuania regulated-entity status and GLEIF LEI matches. Keep each source as a separate table until matching quality is measured, because legal names, codes and regulatory classifications can drift across datasets.

Held-route route: Sodra employer data remains commercially useful, but this cycle’s tested pages did not clear crawler-access QA. Treat Sodra as researched context until a clean data.gov.lt dataset, file endpoint or official API route clears.

Missing-Data Gaps

The open JAR dataset is valuable but narrower than a full certified company dossier. It should not be described as all company filings, all historical documents, all participants, all beneficial owners, all managers, all phone numbers or all emails. VMI data adds taxpayer and tax-context fields, but not a complete legal profile. Bank of Lithuania and GLEIF cover important subsets, not the entire business universe.

The remaining gap is Sodra employment/social-insurance data and beneficial-ownership/participant data. Procurement, active economic entities and trademarks now have clean data.gov.lt replacements, but Sodra still needs a crawlable official route before it can be treated as clean linked evidence. JADIS/JANGIS and beneficial ownership should not be normalized into ordinary company profiles without a separate lawful-use review.

Recommended Data Model

• Entity core: legal-person code, legal name, normalized name, registration date, status where available, country and source confidence.
• JAR provenance: data.gov.lt dataset ID, resource version, format, licence, publisher, access date and update date.
• Public-search provenance: Centre of Registers search URL, query method, manual verification date and limitations.
• Tax enrichment: VMI taxpayer categories, VAT/taxpayer codes, economic activity, paid-tax signals and validity dates in separate tables.
• Regulator and LEI enrichment: Bank of Lithuania category, supervision status, LEI, GLEIF status and issuer/reference dates.
• Procurement/statistics/IP enrichment: VPT contract party, State Data Agency active-entity context, trademark owner/name fields, match confidence and source-date fields.
• Held-source flags: Sodra pending, JADIS/JANGIS special review and marketing-contact blocked.

How CompaniesData Adds Value

CompaniesData.cloud can turn Lithuania’s useful but fragmented official source stack into a practical dataset by normalizing legal-person codes, joining JAR and VMI fields, preserving open-data provenance, separating regulator/LEI enrichment, flagging held sources and keeping contact-data compliance away from public-register assumptions.

For operational users, the value is not a list of Lithuanian portals. The value is a versioned dataset with source dates, licensing notes, deduplicated names, field-level confidence, suppressed or special-review personal data, and delivery formats for CRM enrichment, KYB, procurement research and market mapping.

Request a CompaniesData sample for Lithuania if you need an auditable dataset rather than a source list.

Source-by-Source Deep Dives

JAR raw legal entities dataset on data.gov.lt

Owner: State Enterprise Centre of Registers / data.gov.lt. Access model: public dataset page with CSV, storage API, JSON, JSONL, RDF and CSV resource routes.

Business use: core legal-entity backbone: legal-person code, name and registration-date style fields for registered legal persons

Reuse note: Creative Commons Attribution 4.0 on the data.gov.lt dataset page; preserve attribution and dataset metadata

Limitation: dataset fields are narrower than certified extracts; some business forms are anonymized and certified documents are separate fee/service workflows.

Centre of Registers JAR raw data landing page

Owner: State Enterprise Centre of Registers. Access model: official Centre of Registers landing page for JAR raw data.

Business use: source-owner confirmation for the JAR raw-data route and Centre of Registers provenance

Reuse note: official source page; use alongside the data.gov.lt dataset licence and resources

Limitation: landing-page text is sparse in automated extraction; the data.gov.lt dataset carries the clearer licence/resource evidence.

Public search in the Register of Legal Entities

Owner: State Enterprise Centre of Registers. Access model: public search page; detailed registration data is available to registered users under the service model.

Business use: manual legal-person lookup and current register-search context

Reuse note: official public search context, not a bulk extraction licence; certified data and detailed records follow service rules

Limitation: search access, detailed data and certified extracts are not equivalent to open bulk reuse.

EU e-Justice Lithuania business register profile

Owner: European e-Justice Portal / Lithuania. Access model: official EU profile describing Lithuania's register of legal persons, access, documents and legal effects.

Business use: explains search criteria, public access, documents, fee model, stored fields and data-protection boundaries

Reuse note: context and legal-discovery source; verify operational routes against Centre of Registers and data.gov.lt

Limitation: translation may lag national source changes; it does not replace dataset-level licence review.

data.gov.lt national open data portal

Owner: Lithuanian open data portal / State Digital Solutions Agency. Access model: national catalogue, data warehouse, APIs and dataset discovery.

Business use: discovery layer for registry, tax, public-sector and reusable business datasets

Reuse note: dataset-specific rights; check licence and access rights on each resource

Limitation: portal presence does not prove that every register field is open or reusable.

VMI taxpayer legal-entity dataset

Owner: State Tax Inspectorate under the Ministry of Finance. Access model: public data.gov.lt dataset with storage API, JSON, JSONL, RDF and CSV resource routes.

Business use: taxpayer register context: legal-entity code, name, economic activity, VAT/taxpayer categories and related validity dates

Reuse note: Creative Commons Attribution 4.0 on the dataset page; tax data still needs field-level interpretation and attribution

Limitation: taxpayer data is not the legal register itself and must be reconciled with JAR identifiers.

VMI legal entities paid taxes dataset

Owner: State Tax Inspectorate under the Ministry of Finance. Access model: public data.gov.lt dataset for legal entities' paid taxes.

Business use: tax contribution and public finance context for Lithuanian legal entities

Reuse note: dataset-specific open-data terms; use as financial/tax context rather than legal identity proof

Limitation: paid-tax data is a public-finance signal, not a complete company profile or credit score.

Bank of Lithuania financial market participants

Owner: Bank of Lithuania. Access model: official supervised financial-market participant lists.

Business use: financial-sector compliance enrichment, regulated-entity verification and licence context

Reuse note: sector-specific regulator source; cite Bank of Lithuania and avoid general company-universe claims

Limitation: sector-specific coverage only; absence from this source does not say anything about non-financial companies.

VPT public procurement dataset on data.gov.lt

Owner: Public Procurement Office / State Data Agency via data.gov.lt. Access model: public data.gov.lt dataset with storage API, JSON, JSONL, RDF and CSV resource routes.

Business use: public procurement contracts and parties data from the central procurement contracts subsystem

Reuse note: Creative Commons Attribution 4.0 on the dataset page; use procurement as event/supplier enrichment only

Limitation: procurement covers contracting events and parties, not every Lithuanian company.

State Data Agency active economic entities dataset

Owner: State Data Agency via data.gov.lt. Access model: public data.gov.lt dataset with storage API, JSON, JSONL, RDF and CSV resource routes.

Business use: active economic entities by activity/geography context, useful for coverage and market-size checks

Reuse note: Creative Commons Attribution 4.0 on the dataset page; use as aggregate/statistical context

Limitation: statistics and business demography are not certified legal profiles or all-register documents.

VPB trademarks open data on data.gov.lt

Owner: State Patent Bureau of the Republic of Lithuania via data.gov.lt. Access model: public data.gov.lt dataset with XML source and open-data metadata.

Business use: trademark-owner and IP signal enrichment for Lithuanian legal entities

Reuse note: Creative Commons Attribution 4.0 on the dataset page; official bulletin/legal-force caveat applies

Limitation: IP ownership is partial; owner names can be historical and may lack company codes, so matching must be conservative.

GLEIF LEI records for Lithuania

Owner: GLEIF. Access model: public LEI API and open LEI records.

Business use: LEI cross-checks for Lithuanian legal entities in finance, KYB and compliance workflows

Reuse note: GLEIF open-data/API terms; preserve LEI provenance and timestamps

Limitation: LEI coverage is a subset and does not represent all Lithuanian entities.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
JAR raw legal entities dataset on data.gov.lt	State Enterprise Centre of Registers / data.gov.lt	public dataset page with CSV, storage API, JSON, JSONL, RDF and CSV resource routes	Creative Commons Attribution 4.0 on the data.gov.lt dataset page; preserve attribution and dataset metadata	Clean public source. dataset fields are narrower than certified extracts; some business forms are anonymized and certified documents are separate fee/service workflows.
Centre of Registers JAR raw data landing page	State Enterprise Centre of Registers	official Centre of Registers landing page for JAR raw data	official source page; use alongside the data.gov.lt dataset licence and resources	Clean public source. landing-page text is sparse in automated extraction; the data.gov.lt dataset carries the clearer licence/resource evidence.
Public search in the Register of Legal Entities	State Enterprise Centre of Registers	public search page; detailed registration data is available to registered users under the service model	official public search context, not a bulk extraction licence; certified data and detailed records follow service rules	Conditional context. search access, detailed data and certified extracts are not equivalent to open bulk reuse.
EU e-Justice Lithuania business register profile	European e-Justice Portal / Lithuania	official EU profile describing Lithuania's register of legal persons, access, documents and legal effects	context and legal-discovery source; verify operational routes against Centre of Registers and data.gov.lt	Clean public source. translation may lag national source changes; it does not replace dataset-level licence review.
data.gov.lt national open data portal	Lithuanian open data portal / State Digital Solutions Agency	national catalogue, data warehouse, APIs and dataset discovery	dataset-specific rights; check licence and access rights on each resource	Clean public source. portal presence does not prove that every register field is open or reusable.
VMI taxpayer legal-entity dataset	State Tax Inspectorate under the Ministry of Finance	public data.gov.lt dataset with storage API, JSON, JSONL, RDF and CSV resource routes	Creative Commons Attribution 4.0 on the dataset page; tax data still needs field-level interpretation and attribution	Clean public source. taxpayer data is not the legal register itself and must be reconciled with JAR identifiers.
VMI legal entities paid taxes dataset	State Tax Inspectorate under the Ministry of Finance	public data.gov.lt dataset for legal entities' paid taxes	dataset-specific open-data terms; use as financial/tax context rather than legal identity proof	Clean public source. paid-tax data is a public-finance signal, not a complete company profile or credit score.
Bank of Lithuania financial market participants	Bank of Lithuania	official supervised financial-market participant lists	sector-specific regulator source; cite Bank of Lithuania and avoid general company-universe claims	Clean public source. sector-specific coverage only; absence from this source does not say anything about non-financial companies.
VPT public procurement dataset on data.gov.lt	Public Procurement Office / State Data Agency via data.gov.lt	public data.gov.lt dataset with storage API, JSON, JSONL, RDF and CSV resource routes	Creative Commons Attribution 4.0 on the dataset page; use procurement as event/supplier enrichment only	Clean public source. procurement covers contracting events and parties, not every Lithuanian company.
State Data Agency active economic entities dataset	State Data Agency via data.gov.lt	public data.gov.lt dataset with storage API, JSON, JSONL, RDF and CSV resource routes	Creative Commons Attribution 4.0 on the dataset page; use as aggregate/statistical context	Clean public source. statistics and business demography are not certified legal profiles or all-register documents.
VPB trademarks open data on data.gov.lt	State Patent Bureau of the Republic of Lithuania via data.gov.lt	public data.gov.lt dataset with XML source and open-data metadata	Creative Commons Attribution 4.0 on the dataset page; official bulletin/legal-force caveat applies	Clean public source. IP ownership is partial; owner names can be historical and may lack company codes, so matching must be conservative.
GLEIF LEI records for Lithuania	GLEIF	public LEI API and open LEI records	GLEIF open-data/API terms; preserve LEI provenance and timestamps	Clean public source. LEI coverage is a subset and does not represent all Lithuanian entities.

Resource Pack

Held Sources and Source-Risk Notes

The following sources remain researched but are not treated as clean linked evidence for publication in this cycle.

• Sodra public employer data: browser, Googlebot and Bingbot profiles received a Cloudflare challenge from this environment; keep as researched employment/social-insurance context until a clean data.gov.lt or file route clears. https://sodra.lt/viesi-draudeju-duomenys
• JADIS/JANGIS participants and beneficial ownership: beneficial ownership and participant data can involve natural persons and must remain special-review material with lawful-use, privacy, retention and proportionality checks. https://www.registrucentras.lt/

FAQ

What is the best official starting point for Lithuania company data?

Start with the Centre of Registers and the data.gov.lt JAR registered legal entities dataset. Use public search and EU e-Justice context to understand access, document and fee boundaries.

Does Lithuania publish open company data?

Yes, there is a strong open-data signal through the JAR raw legal entities dataset on data.gov.lt, including public access and Creative Commons Attribution 4.0 on the dataset page. That does not mean every register document or participant field is free or reusable.

Can VMI tax datasets replace the legal-entity register?

No. VMI datasets are valuable enrichment for taxpayer and tax-context fields. They should be joined to the JAR backbone by identifier and kept with their own source provenance.

Why is Sodra still held?

Sodra employer data is commercially useful, but the tested direct pages returned challenge pages to browser and bot profiles from this environment. Procurement, statistics and IP were moved to clean data.gov.lt replacements; Sodra still needs a clean official route.

Can Lithuania public data be used for cold email?

Not automatically. Public register, taxpayer, regulator or LEI data is not marketing consent. Contact-data enrichment requires a separate lawful basis, suppression process and source trail.

Why use CompaniesData for Lithuania?

Lithuania has useful official data, but production use requires matching, provenance, update tracking, privacy flags and held-source handling. CompaniesData packages those steps into a cleaner operational dataset.

Official Sources

• JAR raw legal entities dataset on data.gov.lt – State Enterprise Centre of Registers / data.gov.lt
• Centre of Registers JAR raw data landing page – State Enterprise Centre of Registers
• Public search in the Register of Legal Entities – State Enterprise Centre of Registers
• EU e-Justice Lithuania business register profile – European e-Justice Portal / Lithuania
• data.gov.lt national open data portal – Lithuanian open data portal / State Digital Solutions Agency
• VMI taxpayer legal-entity dataset – State Tax Inspectorate under the Ministry of Finance
• VMI legal entities paid taxes dataset – State Tax Inspectorate under the Ministry of Finance
• Bank of Lithuania financial market participants – Bank of Lithuania
• VPT public procurement dataset on data.gov.lt – Public Procurement Office / State Data Agency via data.gov.lt
• State Data Agency active economic entities dataset – State Data Agency via data.gov.lt
• VPB trademarks open data on data.gov.lt – State Patent Bureau of the Republic of Lithuania via data.gov.lt
• GLEIF LEI records for Lithuania – GLEIF