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

Slovenia is a strong European jurisdiction for official company-data work because AJPES publishes a detailed Slovenian Business Register source page, provides ePRS search, links developer-facing restPrsInfo documentation, and explains data reuse and fee-based data-selection models. That makes Slovenia more than a portal-only country. It has official search, official register structure, API documentation and ordered-data context in one institutional stack.

The practical challenge is that these routes are not the same product. Free ePRS search, electronically signed extracts, web-service extraction, annual-report publication, procurement notices, regulator registers and LEI records each have different legal purposes. A good Slovenia dataset does not flatten them into one unqualified table. It keeps source purpose, field scope, access method, reuse note and confidence visible.

This refresh replaces the older Slovenia page, which was useful as a quick source list but too thin for the current CompaniesData standard. The new article explains methodology, access and update risk, reuse boundaries, API and ordered-data options, missing gaps, a recommended data model, held source-risk findings and the role of CompaniesData normalization.

Key Takeaways

• Best official starting point: AJPES Slovenian Business Register, because it explains PRS, ePRS, data extracts, data reuse and fee-based data selection in one official source.
• Best machine-access evidence: the AJPES restPrsInfo developer manual documents a REST API for direct integration with PRS and JSON/XML input and output options.
• Best filing layer: AJPES JOLP provides annual-report publication context, but annual reports are a filing/enrichment layer rather than the entity core.
• Best enrichment stack: e-JN and ENarocanje support procurement events, GOV.SI/SIPO supports IP authority context, Bank of Slovenia supports regulated financial entities, AVK supports competition events, and GLEIF supports LEI matching.
• Held this cycle: OPSI, SURS, the AJPES order-form PDF route, the SIPO database server, beneficial ownership and contact-data reuse remain held or special-review.
• Contact-data caution: public Slovenian register, annual-report, procurement, regulator, IP or LEI data is not consent for email, phone or sales-prospecting outreach.

Editorial Methodology

The CompaniesData method starts with official sources and then adds enrichment only when authority, access model and reuse limits are explicit. For Slovenia, the editorial order is AJPES PRS/ePRS first, AJPES restPrsInfo API documentation second, AJPES JOLP annual reports third, and then procurement, IP, regulator, competition and LEI sources as enrichment layers.

Every linked source in this article cleared a live source check using browser-like, Googlebot-like and Bingbot-like profiles. HTTP 200 alone was not enough. The source needed expected content semantics, no hard 404/410, no bot-protection title and no obvious challenge page. Routes that were visible in web research but failed local semantics, reset connections or triggered challenge heuristics were held from the linked evidence set.

Source logos in the matrix and Resource Pack are decorative recognition cues loaded through a stable favicon proxy. They are not evidence by themselves. The evidence is the official URL, source owner, access model, reuse note and limitation recorded in the local source-live artifact.

Coverage, Access and Update-Risk Analysis

Registry backbone: PRS is the central Slovenian Business Register database for business entities involved in profit or non-profit activity with their principal place of business in Slovenia. AJPES states that it ensures publicity through ePRS, PRS data extracts and PRS data for reuse. This supports a strong official-company-data claim, but it also proves that access models differ.

Public search and extracts: ePRS is the practical manual route for checking individual entities. The AJPES source page also describes electronically signed extracts and certified routes. Manual search and signed extracts support verification, but they should not be described as a free unrestricted bulk database.

REST/API evidence: restPrsInfo is the strongest technical evidence in the Slovenia stack. The manual describes direct integration with PRS, search and retrieval of official data, minimal/narrow/extended/protected datasets, JSON/XML request bodies, JSON/XML output options and methods for modified or dissolved entities. That supports API-readiness, but implementation still requires endpoint-level terms, credentials, cost, rate and protected-data review.

Ordered and paid data: AJPES describes data reuse fees and data-selection models for PRS units. That is commercially useful because it clarifies that official bulk or web-service routes may be ordered or charged rather than freely scraped. Any derived product should store the order route, fee basis, update cadence, data structure and customer-use restrictions.

Enrichment layers: JOLP annual reports, procurement, Bank of Slovenia supervised entities, AVK competition decisions, SIPO authority context and GLEIF LEI data are all useful, but they cover different business questions. They should enrich the PRS core rather than replace it.

Reuse Checklist

• Authority check: record whether each field came from AJPES PRS/ePRS, restPrsInfo, JOLP, e-JN, ENarocanje, SIPO, Bank of Slovenia, AVK or GLEIF.
• Access check: separate free search, signed extracts, REST/web-service access, ordered data selection, annual-report search, procurement events, regulator lists and LEI API data.
• Licence and fee check: preserve AJPES reuse terms, order basis, fee category, update cadence, source date and no-endorsement wording for each resource actually ingested.
• Field-scope check: do not merge minimal, narrow, extended or protected datasets without clear field-level permissions and purpose notes.
• Personal-data check: representatives, founders, sole proprietors, beneficial owners and contact fields require GDPR, retention, suppression and lawful-use review.
• Crawler check: if a source or sitemap returns a challenge, HTML instead of XML, 403, 415, bot-protection title or a hard error to crawler profiles, hold the route until retested.
• Marketing check: public register visibility is not permission for cold email, phone calls, lead lists or sales-prospecting databases.

Practical Manual, API and Bulk Options

Manual verification: use ePRS and the AJPES Slovenian Business Register route for entity-level checks, status verification, registration-number matching and manual due diligence. This route is appropriate when a person needs to inspect one company or resolve a disputed match.

REST API planning: use the restPrsInfo manual for machine-ingestion planning. A production workflow should store method names, dataset type, input format, output format, authentication or contract status, response parser version, error handling and change-detection logic.

Ordered data and reuse: use AJPES PRS reuse and fee information as the commercial access context. Do not scrape around an ordered-data model. If a project needs large-scale PRS extraction, document the selected data structure, fee schedule, billing model, update frequency and permitted use.

Annual-report enrichment: use JOLP to add financial-report and filing signals. Store annual-report references as a separate table with filing date, report type and source route. Do not treat a missing annual report as proof that a company does not exist.

Procurement and regulator enrichment: use e-JN, ENarocanje, Bank of Slovenia and AVK as event or sector-specific layers. These sources are powerful for public-sector sales, regulated financial screening and competition-law due diligence, but they are not comprehensive registers.

Source-by-Source Deep Dives

1. AJPES Slovenian Business Register

Owner: AJPES. Access model: official PRS register page describing ePRS access, extracts, reuse and data-fee routes. Reuse note: official register source; reuse depends on ePRS terms, data-selection fees, order/contract route and field scope

Business use: legal-entity backbone, identifier matching, register scope, data-reuse policy and data-structure context In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: free search, extracts, web-service extraction and full-data selection are different access models This source cleared the current linked-source publication gate. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

2. AJPES ePRS portal

Owner: AJPES. Access model: public ePRS search route for individual Slovenian Business Register entities. Reuse note: manual/public-search route; acquired data must follow AJPES terms and source restrictions

Business use: manual verification, search fallback and entity-level reconciliation In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: search portal use is not the same as ordered bulk data or unrestricted API reuse This source cleared the current linked-source publication gate. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

3. AJPES restPrsInfo developer manual

Owner: AJPES. Access model: REST API documentation for direct integration with PRS, including JSON/XML input and output options. Reuse note: technical documentation supports API-integration claims, but production use still requires terms, access and cost review

Business use: machine-readable ingestion planning, endpoint mapping, update monitoring and parser design In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: API documentation is not a blanket permission to republish every field or protected dataset This source cleared the current linked-source publication gate. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

4. AJPES JOLP annual reports

Owner: AJPES. Access model: public search and publication route for annual reports and business-information filings. Reuse note: filing-source terms apply; store annual-report provenance separately from PRS core identity

Business use: financial-statement discovery, filing enrichment and company-event research In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: annual reports are a filing layer, not a complete register or contact-data source This source cleared the current linked-source publication gate. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

5. e-JN electronic public procurement

Owner: Government of Slovenia. Access model: electronic public procurement system route. Reuse note: procurement-specific terms apply; cite procurement provenance and avoid all-company coverage claims

Business use: public-sector supplier-event enrichment and procurement workflow context In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: procurement activity is event-based and covers suppliers or contracting workflows, not the whole company universe This source is included as conditional context because procurement coverage is event-based. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

6. ENarocanje public procurement portal

Owner: Portal javnih naročil / Slovenia. Access model: public procurement notices and award-discovery portal. Reuse note: event-level public procurement source; automated reuse needs notice and portal terms review

Business use: tender, award, buyer and supplier enrichment In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: supplier-only and event-only coverage; not a legal register or ownership source This source is included as conditional context because procurement coverage is event-based. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

7. Slovenian Intellectual Property Office on GOV.SI

Owner: Slovenian Intellectual Property Office / GOV.SI. Access model: official GOV.SI page for the Slovenian Intellectual Property Office and IP service areas. Reuse note: official IP context; IP records and right-owner data need their own route and terms

Business use: IP authority context, trademark/patent/design enrichment routing and source ownership In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: authority profile is not a bulk IP database and rights ownership can differ from legal-company identity This source cleared the current linked-source publication gate. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

8. Bank of Slovenia supervised entities

Owner: Bank of Slovenia. Access model: register of supervised entities and regulated financial-sector categories. Reuse note: sector-specific regulator source; store category, authority and date separately from PRS core

Business use: financial-sector compliance enrichment and regulated-entity screening In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: sector-specific; includes non-Slovenian EEA entities and does not represent all Slovenian companies This source cleared the current linked-source publication gate. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

9. Slovenian Competition Protection Agency

Owner: Slovenian Competition Protection Agency. Access model: competition-law decisions, concentrations, antitrust and agency news. Reuse note: decision/event source; cite case provenance and avoid complete-coverage claims

Business use: competition-law event enrichment, market-risk context and due-diligence signals In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: case-driven coverage and legal-event focus, not a company-register substitute This source cleared the current linked-source publication gate. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

10. GLEIF LEI records for Slovenia

Owner: GLEIF. Access model: public JSON API for LEI-bearing Slovenian entities. Reuse note: GLEIF API terms and attribution apply; use as enrichment and identifier cross-check only

Business use: LEI crosswalk, financial-entity matching and structured legal-entity metadata In a CompaniesData workflow, this source should be stored with owner, URL, access date, native identifier, field scope, language, parser version and confidence before it is joined to another Slovenian source.

Limitations: LEI coverage is partial and only includes entities that have LEIs This source cleared the current linked-source publication gate. Do not stretch it into full-company coverage, beneficial ownership, credit-score, certified-extract or marketing-consent claims.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
AJPES Slovenian Business Register	AJPES	official PRS register page describing ePRS access, extracts, reuse and data-fee routes	official register source; reuse depends on ePRS terms, data-selection fees, order/contract route and field scope	Clean public source. free search, extracts, web-service extraction and full-data selection are different access models
AJPES ePRS portal	AJPES	public ePRS search route for individual Slovenian Business Register entities	manual/public-search route; acquired data must follow AJPES terms and source restrictions	Clean public source. search portal use is not the same as ordered bulk data or unrestricted API reuse
AJPES restPrsInfo developer manual	AJPES	REST API documentation for direct integration with PRS, including JSON/XML input and output options	technical documentation supports API-integration claims, but production use still requires terms, access and cost review	Clean public source. API documentation is not a blanket permission to republish every field or protected dataset
AJPES JOLP annual reports	AJPES	public search and publication route for annual reports and business-information filings	filing-source terms apply; store annual-report provenance separately from PRS core identity	Clean public source. annual reports are a filing layer, not a complete register or contact-data source
e-JN electronic public procurement	Government of Slovenia	electronic public procurement system route	procurement-specific terms apply; cite procurement provenance and avoid all-company coverage claims	Conditional context. procurement activity is event-based and covers suppliers or contracting workflows, not the whole company universe
ENarocanje public procurement portal	Portal javnih naročil / Slovenia	public procurement notices and award-discovery portal	event-level public procurement source; automated reuse needs notice and portal terms review	Conditional context. supplier-only and event-only coverage; not a legal register or ownership source
Slovenian Intellectual Property Office on GOV.SI	Slovenian Intellectual Property Office / GOV.SI	official GOV.SI page for the Slovenian Intellectual Property Office and IP service areas	official IP context; IP records and right-owner data need their own route and terms	Clean public source. authority profile is not a bulk IP database and rights ownership can differ from legal-company identity
Bank of Slovenia supervised entities	Bank of Slovenia	register of supervised entities and regulated financial-sector categories	sector-specific regulator source; store category, authority and date separately from PRS core	Clean public source. sector-specific; includes non-Slovenian EEA entities and does not represent all Slovenian companies
Slovenian Competition Protection Agency	Slovenian Competition Protection Agency	competition-law decisions, concentrations, antitrust and agency news	decision/event source; cite case provenance and avoid complete-coverage claims	Clean public source. case-driven coverage and legal-event focus, not a company-register substitute
GLEIF LEI records for Slovenia	GLEIF	public JSON API for LEI-bearing Slovenian entities	GLEIF API terms and attribution apply; use as enrichment and identifier cross-check only	Clean public source. LEI coverage is partial and only includes entities that have LEIs

Resource Pack

Missing-Data Gaps

The main Slovenia gap is not the absence of official sources. It is the need to respect separate access products. PRS public search, PRS extracts, restPrsInfo web-service extraction, ordered data selection, annual reports, procurement events, regulator records, competition decisions and LEI records all answer different questions. A derived dataset needs field-level provenance rather than one generic source label.

Protected and personal data are another gap. AJPES materials distinguish data structures and protected datasets. Representatives, founders, sole proprietors, beneficial owners, contact details and documents can involve natural persons. Those fields require lawful-basis, retention and suppression controls before commercial reuse.

Two useful context routes stayed out of the linked-source core in this cycle. OPSI was visible through web research but local challenge heuristics flagged the route. SURS was visible through web research but local requests reset. Both may be useful later, but they should not be used as clean publication evidence until the source QA is repeated successfully.

Recommended Data Model

• Entity core: registration number, legal name, normalized name, tax number where lawful, legal form, status, address fields where allowed, country, source date and confidence.
• PRS provenance: AJPES source route, ePRS/manual or restPrsInfo/API method, data-structure level, field list, ordered-data status, fee/order note and update timestamp.
• Extract and document layer: signed extract route, document type, file reference, issuance date, authenticity note and retention rule.
• Annual-report layer: JOLP report reference, reporting period, publication date, filing type, parser version and financial-field confidence.
• Procurement layer: e-JN or ENarocanje notice, contracting authority, supplier, procedure reference, award/contract event and match confidence.
• Regulator and competition layer: Bank of Slovenia category, AVK decision/event reference, source URL, event date and sector-specific limitation.
• LEI layer: LEI, GLEIF legal name, entity status, registration authority reference, address data and match confidence.
• Privacy controls: personal-data flag, beneficial-ownership special-review flag, protected-dataset flag, suppression marker and marketing-contact block.

How CompaniesData Adds Value

CompaniesData.cloud adds value by turning Slovenia’s strong official source stack into a normalized, auditable data product. The work is not just copying AJPES links. It is matching PRS identifiers with names and tax fields, preserving the distinction between public search and ordered data, parsing annual-report and procurement signals separately, joining regulator and LEI enrichment conservatively, and keeping personal or protected data out of broad commercial exports unless a lawful-use review clears it.

For commercial teams, this supports KYB, CRM enrichment, market sizing, public-sector sales research, supplier discovery and regulated-sector screening. For compliance teams, it keeps source owner, access date, fee/order basis, field scope, confidence and held-source notes visible. For data teams, it reduces time spent interpreting Slovenian labels, choosing between public search and API access, and reconciling company names across register, filing, procurement and LEI layers.

For English and international workflows, request a CompaniesData sample for Slovenia if you need a practical dataset rather than a list of portals. For Spanish-speaking or Hispanic contact-data workflows, CentraldeComunicacion.es is the preferred owned property. Do not treat Slovenian official-source visibility as permission for direct email, phone lists or lead-list resale.

Held Sources and Source-Risk Notes

The following routes were researched but are not treated as clean linked publication evidence in this cycle.

• AJPES PRS data order form: verified in web research as the official order route, but held from the linked matrix because local semantic PDF parsing did not clear all expected terms.
• Slovenia open-data portal OPSI: browser and bot-profile checks saw real content but local challenge heuristics flagged the route; keep as research context until a clean source QA pass is recorded.
• SURS Statistical Office: web research showed the public SURS site, but local browser and bot-profile requests reset; do not link as clean evidence in this cycle.
• SIPO information database server: official-looking IP database route was reachable but local semantics did not clear; use the GOV.SI SIPO authority profile instead.
• Register of beneficial owners: beneficial ownership involves natural persons, AML purpose limits, privacy, access and lawful-use constraints; special-review only.
• Private contact-data and outreach lists: public registry, procurement, regulator or LEI data is not consent for email, phone or sales-prospecting use.

FAQ

What is the best official source for Slovenia company data?

Start with AJPES and the Slovenian Business Register. It explains PRS, ePRS public access, extracts, data reuse and developer links in one official source.

Does Slovenia have an official API for company data?

Yes. AJPES publishes restPrsInfo developer documentation for direct integration with PRS, including JSON/XML options and methods for searching, retrieving and monitoring changed or dissolved entities. Production use still needs terms, access and cost review.

Is ePRS a bulk download?

No. ePRS is a public-search route for individual entities. AJPES also describes data extracts, web-service extraction and data selection for reuse, which can involve ordered or fee-based access.

Can annual reports replace the business register?

No. AJPES JOLP annual reports are an important filing layer, but they should enrich the PRS entity core rather than replace legal-register identity.

Can public Slovenian company data be reused commercially?

It can support commercial analysis when the specific source terms, fee/order model, attribution and privacy limits are respected. Public visibility is not the same as unrestricted all-fields reuse.

Can I use Slovenian registry data for cold email?

No automatic permission follows from public registry access. Email, phone and lead-list enrichment require a separate lawful basis, suppression handling and contact-data compliance process.

Why use CompaniesData for Slovenia?

Slovenia has strong official sources, but they are split across PRS, ePRS, API/order models, annual reports, procurement, regulators, competition and LEI data. CompaniesData normalizes identifiers, joins sources conservatively, stores provenance and separates legal-entity identity from contact-data permission.

Official Sources

• AJPES Slovenian Business Register – AJPES
• AJPES ePRS portal – AJPES
• AJPES restPrsInfo developer manual – AJPES
• AJPES JOLP annual reports – AJPES
• e-JN electronic public procurement – Government of Slovenia
• ENarocanje public procurement portal – Portal javnih naročil / Slovenia
• Slovenian Intellectual Property Office on GOV.SI – Slovenian Intellectual Property Office / GOV.SI
• Bank of Slovenia supervised entities – Bank of Slovenia
• Slovenian Competition Protection Agency – Slovenian Competition Protection Agency
• GLEIF LEI records for Slovenia – GLEIF