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

Eswatini has a usable official-source trail for company-data work, but it should not be described as a country with a complete free official bulk company database. The reliable path starts with the Registrar of Companies and the Government Online Services company workflows, then adds the Eswatini Trade Information Portal, Eswatini Revenue Service, ESPPRA, the Central Statistics Office, financial regulators, listed-securities context and GLEIF LEI records.

The practical answer for data buyers is clear: Eswatini is a multi-source verification jurisdiction, not an open-bulk registry jurisdiction. Public pages explain how company names, registration and compliance workflows operate, but a commercial dataset still needs normalization, matching, source provenance and a strict separation between official public records and private contact-data enrichment.

Key Takeaways

• Best starting point: use the Registrar of Companies page and Government Online Services for company-name and registration workflow evidence.
• No bulk claim: this refresh did not verify a complete free official company-register bulk file or public company API for all Eswatini entities.
• Strong supporting layers: ESPPRA, ERS, the Central Statistics Office, the Central Bank, FSRA, the Eswatini Stock Exchange and GLEIF help enrich procurement, tax, sector and cross-border identity context.
• Source-risk finding: the business.gov.sz reform portal was held because it presented a certificate mismatch and redirected to an elections site during live QA.
• Marketing caution: registry, tax, procurement and regulator sources do not create consent for business-email lists, phone lists or sales-prospecting extraction. International contact-data work should route through CompaniesData.cloud.

Editorial Methodology

This refresh follows the CompaniesData open-company-data standard: official sources first, source claims scoped to what the source actually provides, and publication blocked when a link is unstable for normal browser and crawler profiles. The Eswatini source set was rechecked on 13 June 2026 with browser, Googlebot and Bingbot user agents. Thirteen sources passed as publication-safe links and three were held as research-only sources.

Sources were classified by authority, access model, reuse uncertainty, operational value and source risk. Registry workflow sources rank above procurement, statistics and regulator layers. Sector regulators and GLEIF are used for enrichment, not as substitutes for the Registrar of Companies. High-quality procedural pages are included only where they clarify official workflows and remain reachable to crawlers.

• Included: registrar, online-services workflow, company-name search, company-registration workflow, trade-procedure page, procurement, tax, statistics, banking, non-bank financial services, stock exchange and LEI records.
• Held back: company-name reservation, business.gov.sz and the ESPPRA tender subpage were not linked in the article source set because the probe found timeout, redirect or stability issues.
• Access date: source checks and crawler-profile notes are dated 13 June 2026.

Coverage, Access and Update-Risk Analysis

The Registrar of Companies is the strongest legal-identity source because it describes the mandate, Companies Act basis and company-registration function. Government Online Services and the company-name search and company-registration pages provide the practical online workflow. Together they support claims about how company names and registrations are handled, but they do not publish a full downloadable company master table.

The supporting ecosystem is useful but fragmented. ERS helps with tax-registration and compliance context; ESPPRA helps identify public-procurement activity; the Central Statistics Office gives aggregate economic context; the Central Bank and FSRA identify regulated-sector context; the Eswatini Stock Exchange identifies listed securities and issuer context; and GLEIF provides a clean API for the small subset of entities with LEIs.

Update risk: workflow pages may change without dataset changelogs, regulator lists can change by supervisory cycle, procurement notices update by tender cadence, and GLEIF updates independently from domestic systems. A production dataset should store source URL, access timestamp, crawler-profile result, field-level provenance and a freshness score instead of assuming all layers move together.

Reuse Checklist

• Public search and service pages: useful for verification and workflow documentation, but not evidence of unrestricted commercial bulk reuse.
• Registration workflows: use as process evidence unless a specific record, certificate or extract is lawfully obtained and licensed for the intended use.
• API and bulk access: no complete official company-register API or bulk file was verified; GLEIF is the clean API layer for LEI-bearing entities only.
• Procurement data: use for public-sector supplier and tender context, not as proof that a company is active or incorporated.
• Tax and regulated-sector data: apply purpose limits, confidentiality rules and sector-specific caveats.
• Private contact data: business emails, phone lists and lead lists must be handled separately through CompaniesData.cloud with lawful-use checks.
• No endorsement: do not imply that Eswatini authorities endorse a normalized commercial dataset.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Practical value	Limitations
Registrar of Companies – Eswatini Government	Registrar of Companies, Ministry of Commerce, Industry and Trade	public government department page plus linked online company services	Government site terms and the Companies Act service rules; no bulk reuse licence found	Primary official authority for company formation, company names and company-registration workflow.	Authority and service context only; not a complete downloadable register of all companies.
Government Online Services	Government Computer Services / Government Online Services	public online-services portal with business-registration menu	Portal service terms; public interaction is not a bulk download or API grant	Navigation layer for company name search, company registration and related e-government business services.	Workflow portal, not a structured open-data export.
Company Name Search – Government Online Services	Government Online Services company name search	public search form for company-name checking	Search-form terms and ordinary fair-use citation; no evidence of machine bulk reuse	Practical first check for name availability or name matching before deeper manual verification.	A name-search form does not prove full registration status, ownership, filings or full company population coverage.
Company Registration – Government Online Services	Government Online Services company registration	public registration login and new-registration workflow	Service workflow terms; login or form access does not imply scraping permission	Shows the current online route for registration and document-flow planning.	Login workflow, not a public register, bulk endpoint or API.
Eswatini Trade Information Portal company name search procedure	Eswatini Trade Information Portal	public procedure page describing the company-name search route	Portal publication terms and procedure-page attribution	Provides an official procedural explanation that helps users understand the registry workflow.	Procedure guide only; it does not publish the company population.
ESPPRA	Eswatini Public Procurement Regulatory Agency	public procurement authority portal and notices	Procurement-publication rules and ESPPRA site terms	Supplier, tender, procurement-plan and public-spending context for entities already known from other sources.	Procurement participation is not incorporation status and is biased toward public-sector suppliers.
Eswatini Revenue Service	Eswatini Revenue Service	public tax-service, registration and guidance portal	Tax confidentiality, ERS site terms and purpose-limited public guidance	Taxpayer-registration and compliance context for already-known entities and business workflows.	Tax data is not an open marketing list and usually cannot be repurposed beyond lawful verification.
Central Statistics Office – Eswatini Government	Central Statistics Office	public government statistics office page and reports	Government publication terms and report-specific attribution	Sector, economic and business-environment context for modelling and coverage estimates.	Aggregate statistics do not identify individual companies.
Central Bank of Eswatini	Central Bank of Eswatini	public central-bank portal and publications	Central-bank publication terms and financial-regulation limits	Banking-sector and financial-system context for regulated entities.	Sector-specific and not a substitute for the company register.
Central Bank of Eswatini bank supervision	Central Bank of Eswatini banking supervision	public bank-supervision page	Central-bank publication terms and supervisory-use limits	Bank-supervision context and regulated-entity review for financial institutions.	Useful only for supervised-bank context, not all companies.
Financial Services Regulatory Authority Eswatini	Financial Services Regulatory Authority	public non-bank financial services regulator portal and licensed-entity navigation	FSRA site terms and financial-services regulatory limits	Non-bank financial services provider context: insurance, retirement funds, credit, SACCOs and investment sectors.	Regulated-sector subset; not a complete registry of commercial companies.
Eswatini Stock Exchange listed securities	Eswatini Stock Exchange	public listed-securities page	Exchange site terms, market-data terms and no-endorsement cautions	Listed issuer and securities-market context for public companies and instruments.	Tiny listed universe and securities-level data, not a general company register.
GLEIF LEI records for Eswatini	Global Legal Entity Identifier Foundation	public LEI API and downloadable reference data	GLEIF open data licence	Cross-border LEI enrichment for the small subset of Eswatini entities that hold LEIs.	Partial population, skewed toward financial and cross-border entities; not a national registry.

Source-by-Source Deep Dives

Registrar of Companies – Eswatini Government

Authority and coverage: Registrar of Companies, Ministry of Commerce, Industry and Trade is treated as a registry layer. It contributes legal formation route, company-registration procedure, company-name protection and service contacts. The safe claim is narrow: Primary official authority for company formation, company names and company-registration workflow.

Access model and reuse: The live route is public government department page plus linked online company services. Reuse should follow Government site terms and the Companies Act service rules; no bulk reuse licence found. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Anchor every Eswatini legal-entity record to a registrar provenance note before adding tax, procurement or regulator enrichment. Authority and service context only; not a complete downloadable register of all companies. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Department pages can change without a dataset changelog, so access date and source URL need to be stored with each derived claim.

Government Online Services

Authority and coverage: Government Computer Services / Government Online Services is treated as a registry layer. It contributes service menu, business workflow entry points and online-registration context. The safe claim is narrow: Navigation layer for company name search, company registration and related e-government business services.

Access model and reuse: The live route is public online-services portal with business-registration menu. Reuse should follow Portal service terms; public interaction is not a bulk download or API grant. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Treat portal pages as workflow evidence, not as entity-level records unless a search result or document is separately captured. Workflow portal, not a structured open-data export. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Menu items and form endpoints can be renamed or moved, so crawler QA must check semantics rather than only HTTP status.

Company Name Search – Government Online Services

Authority and coverage: Government Online Services company name search is treated as a registry layer. It contributes submitted name, search workflow and possible name-availability evidence. The safe claim is narrow: Practical first check for name availability or name matching before deeper manual verification.

Access model and reuse: The live route is public search form for company-name checking. Reuse should follow Search-form terms and ordinary fair-use citation; no evidence of machine bulk reuse. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Use for candidate-name matching and false-positive reduction, then confirm legal identity through registrar or document workflows. A name-search form does not prove full registration status, ownership, filings or full company population coverage. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Interactive forms may rate-limit or time out; QA needs browser and bot-profile checks before public linking.

Company Registration – Government Online Services

Authority and coverage: Government Online Services company registration is treated as a registry layer. It contributes registration workflow, login/new-registration context and reprint path. The safe claim is narrow: Shows the current online route for registration and document-flow planning.

Access model and reuse: The live route is public registration login and new-registration workflow. Reuse should follow Service workflow terms; login or form access does not imply scraping permission. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Use as process evidence for how new companies enter the official system, not as a source for finished entity rows. Login workflow, not a public register, bulk endpoint or API. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Form behavior can change independently from the department page.

Eswatini Trade Information Portal company name search procedure

Authority and coverage: Eswatini Trade Information Portal is treated as a procedure layer. It contributes procedure steps, responsible agency context and business-startup workflow. The safe claim is narrow: Provides an official procedural explanation that helps users understand the registry workflow.

Access model and reuse: The live route is public procedure page describing the company-name search route. Reuse should follow Portal publication terms and procedure-page attribution. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Use to document process provenance and reconcile registry tasks with practical user workflows. Procedure guide only; it does not publish the company population. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Procedure pages can lag live portal forms, so compare against Government Online Services before operational use.

ESPPRA

Authority and coverage: Eswatini Public Procurement Regulatory Agency is treated as a procurement layer. It contributes procuring entity, tender context, award or plan references where published. The safe claim is narrow: Supplier, tender, procurement-plan and public-spending context for entities already known from other sources.

Access model and reuse: The live route is public procurement authority portal and notices. Reuse should follow Procurement-publication rules and ESPPRA site terms. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Link procurement names to registry candidates only with confidence scoring and source provenance. Procurement participation is not incorporation status and is biased toward public-sector suppliers. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Tender subpages can be more fragile than the authority homepage; held tender URLs need retesting before linking.

Eswatini Revenue Service

Authority and coverage: Eswatini Revenue Service is treated as a tax layer. It contributes tax registration guidance, VAT/income-tax context, public-officer and business-tax workflows. The safe claim is narrow: Taxpayer-registration and compliance context for already-known entities and business workflows.

Access model and reuse: The live route is public tax-service, registration and guidance portal. Reuse should follow Tax confidentiality, ERS site terms and purpose-limited public guidance. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Keep tax identifiers and tax status in a restricted compliance layer with explicit legal-use flags. Tax data is not an open marketing list and usually cannot be repurposed beyond lawful verification. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: ERS used an SSL-unverified retry in the source probe but returned real semantics across profiles.

Central Statistics Office – Eswatini Government

Authority and coverage: Central Statistics Office is treated as a statistics layer. It contributes economic, demographic and statistical-publication context. The safe claim is narrow: Sector, economic and business-environment context for modelling and coverage estimates.

Access model and reuse: The live route is public government statistics office page and reports. Reuse should follow Government publication terms and report-specific attribution. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Use CSO terms to standardize sectors and market context, not as a legal-entity source. Aggregate statistics do not identify individual companies. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: PDF/report cadence can differ from registry workflow changes.

Central Bank of Eswatini

Authority and coverage: Central Bank of Eswatini is treated as a regulated layer. It contributes central-bank publications, policy context and regulated-sector references. The safe claim is narrow: Banking-sector and financial-system context for regulated entities.

Access model and reuse: The live route is public central-bank portal and publications. Reuse should follow Central-bank publication terms and financial-regulation limits. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Use the central bank as a regulated-sector layer with its own provenance and date. Sector-specific and not a substitute for the company register. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Some pages expose limited text to crawlers; semantic QA should look for authority and page-title evidence.

Central Bank of Eswatini bank supervision

Authority and coverage: Central Bank of Eswatini banking supervision is treated as a regulated layer. It contributes bank-supervision function, supervisory context and banking-sector evidence. The safe claim is narrow: Bank-supervision context and regulated-entity review for financial institutions.

Access model and reuse: The live route is public bank-supervision page. Reuse should follow Central-bank publication terms and supervisory-use limits. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Attach as a sector flag after legal-entity matching, not as a source of universal company records. Useful only for supervised-bank context, not all companies. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Bank-supervision pages may move under financial-regulation navigation.

Financial Services Regulatory Authority Eswatini

Authority and coverage: Financial Services Regulatory Authority is treated as a regulated layer. It contributes licensed-entity navigation, deregistered/intervention context and regulatory mandate. The safe claim is narrow: Non-bank financial services provider context: insurance, retirement funds, credit, SACCOs and investment sectors.

Access model and reuse: The live route is public non-bank financial services regulator portal and licensed-entity navigation. Reuse should follow FSRA site terms and financial-services regulatory limits. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Use FSRA as a regulated-entity enrichment layer after resolving the legal name. Regulated-sector subset; not a complete registry of commercial companies. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Licensed-entity pages and documents may change by sector and by supervisory cycle.

Eswatini Stock Exchange listed securities

Authority and coverage: Eswatini Stock Exchange is treated as a regulated layer. It contributes listed securities, issuer context, market data and securities identifiers. The safe claim is narrow: Listed issuer and securities-market context for public companies and instruments.

Access model and reuse: The live route is public listed-securities page. Reuse should follow Exchange site terms, market-data terms and no-endorsement cautions. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Map listed names to legal entities and store securities fields separately from company master data. Tiny listed universe and securities-level data, not a general company register. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: Market values and listed-security pages can update frequently and need timestamped capture.

GLEIF LEI records for Eswatini

Authority and coverage: Global Legal Entity Identifier Foundation is treated as a lei layer. It contributes LEI, legal name, legal address, registration status and reference-data metadata. The safe claim is narrow: Cross-border LEI enrichment for the small subset of Eswatini entities that hold LEIs.

Access model and reuse: The live route is public LEI API and downloadable reference data. Reuse should follow GLEIF open data licence. Public visibility here does not create a general right to scrape, resell or convert the material into a marketing list.

Normalization issue: Use as high-confidence enrichment where an LEI exists, but do not infer absence for non-LEI companies. Partial population, skewed toward financial and cross-border entities; not a national registry. Operationally, CompaniesData should store source URL, access date, crawler result and field-level provenance for every value derived from this layer.

Update risk: GLEIF updates daily, while domestic registry workflows may not expose the same cadence.

Practical Manual, API and Bulk Options

• Manual verification route: start with the Registrar of Companies and Government Online Services. Capture the source URL, search term, request date, document reference and outcome. Use the Trade Information Portal procedure page to explain the workflow to non-local users.
• API route: use GLEIF for LEI-bearing Eswatini entities. Store LEI, legal name, address, registration status and GLEIF update date, but mark coverage as partial because only a small subset of entities hold LEIs.
• Procurement route: use ESPPRA to enrich already-known entities with tender, procurement-plan or supplier context. Keep procurement evidence separate from incorporation status.
• Tax route: use ERS guidance for tax-registration and compliance modelling only where lawful. Do not treat tax pages as open contact-data sources.
• Regulated-sector route: use the Central Bank, FSRA and the Eswatini Stock Exchange for banks, non-bank financial providers and listed issuers. These are high-value quality-control layers for regulated companies.
• Bulk route: because no complete official company-register bulk file was verified, any commercial bulk dataset should be described as normalized multi-source coverage, not as a direct official registry dump.
• Contact-data route: contact enrichment belongs in a separate lawful-use product flow through CompaniesData.cloud, with opt-out, suppression and purpose controls.

What Is Missing from Official Open Data?

The main missing piece is a complete, downloadable, official company register with stable identifiers, company status, incorporation date, historical names, directors or officers where lawful, addresses, event history and update timestamps. The public workflow pages show how registration and search work, but they do not expose all entity-level fields in a reusable data package.

Beneficial ownership was not verified as a public reusable dataset in this refresh. Officer or contact-person details, if encountered through documents or workflows, need separate legal and privacy review. Procurement and regulator records help confirm business activity, but they are not universal and can overrepresent suppliers, banks, insurers, retirement funds, listed issuers and entities active in formal regulated channels.

The held business.gov.sz portal is also a source-risk gap. It looked relevant by name, but the live QA found a certificate mismatch and redirect to an elections site, so it should not be cited as a business-registry source until the domain, certificate and content semantics are repaired.

Recommended Data Model

• Entity identity: legal name, normalized name, aliases, country, entity type, status when verified, confidence score and registry-workflow provenance.
• Source provenance: source owner, source URL, access date, crawler-profile result, field-level provenance, reuse note and no-endorsement flag.
• Identifiers: registrar reference where lawfully available, tax-context flag where usable, LEI, procurement identifiers, listed-securities identifiers and CompaniesData internal match key.
• Evidence events: registration workflow evidence, procurement event, regulated-sector listing, stock-exchange listing, LEI update and manual-document verification event.
• Risk and quality fields: source freshness, dedupe status, name-match confidence, source-risk flag, privacy flag, contact-data eligibility flag and lawful-use notes.
• Delivery fields: public-source package, compliance-review package and separately lawful contact-data package should be clearly separated.

CompaniesData Normalization and Enrichment Value

CompaniesData adds value in Eswatini because the useful official evidence is spread across workflows and sector portals. A buyer does not only need links. They need deduplicated legal names, source provenance, matching between registry names and procurement or regulator names, sector labels, freshness tracking and a clear explanation of what cannot be proven from public sources.

Where CompaniesData helps: CompaniesData can normalize entity names, preserve source evidence, reconcile LEI and regulator records, add procurement or listed-issuer context, flag incomplete coverage and keep marketing-contact data out of the public-registry evidence layer. This makes the dataset more auditable for data buyers, compliance reviewers and internal sales operations.

Request a CompaniesData sample for Eswatini if you need a practical company dataset rather than a manual list of portals.

Grouped Resource Pack

Source-Risk Notes and Held Sources

• Company Name Reservation – Government Online Services: Googlebot timed out in the source probe; use Company Name Search and Company Registration instead until retested URL tested: https://online.gov.sz/e-reservationSignOn.aspx
• Business registry reform portal: certificate mismatch and redirect to an elections site, so it is not publication-safe as a business-registry source URL tested: https://business.gov.sz/
• ESPPRA tender opportunities: tender subpage was unstable in the live probe; ESPPRA homepage remains linked as the safer procurement authority source URL tested: https://esppra.co.sz/sppra/tender.php

FAQ

Is there a single free official bulk company database for Eswatini?

No. This refresh verified official workflow and enrichment sources, but not a complete free official company-register bulk file or API for all entities.

What is the best first source?

Start with the Registrar of Companies and Government Online Services. Use the company-name search and company-registration pages for workflow evidence, then add ERS, ESPPRA, CSO, Central Bank, FSRA, ESE and GLEIF as supporting layers.

Can CompaniesData use these sources commercially?

Commercial reuse depends on source terms, field type and purpose. Public access does not equal unrestricted reuse. A commercial dataset should preserve attribution, source URL, access date, field provenance and no-endorsement language.

Can registry or tax data be used for email marketing?

No. Registry, tax, procurement and regulator data are verification sources, not consent for business emails, phone lists or lead lists. Contact-data enrichment must be handled separately through CompaniesData.cloud with lawful-use checks.

How often should an Eswatini dataset be refreshed?

Refresh cadence should be source-specific. Registry workflow links and search forms need frequent checks, procurement notices can move by tender cycle, regulator lists change by supervisory cycle, statistics follow report releases and GLEIF can be refreshed through its API.

Why include regulators and GLEIF if they are not the registry?

They improve entity resolution and risk review. A bank, insurer, pension-fund provider, listed issuer or LEI-bearing entity may need sector context that the company-registration workflow alone does not provide.

Why was business.gov.sz held?

The domain looked relevant, but live QA found certificate and redirect problems that led to an elections site. It should stay research-only until the official business-registry semantics are restored.

Official Sources

• Registrar of Companies – Eswatini Government – Registrar of Companies, Ministry of Commerce, Industry and Trade; public government department page plus linked online company services; reuse note: Government site terms and the Companies Act service rules; no bulk reuse licence found.
• Government Online Services – Government Computer Services / Government Online Services; public online-services portal with business-registration menu; reuse note: Portal service terms; public interaction is not a bulk download or API grant.
• Company Name Search – Government Online Services – Government Online Services company name search; public search form for company-name checking; reuse note: Search-form terms and ordinary fair-use citation; no evidence of machine bulk reuse.
• Company Registration – Government Online Services – Government Online Services company registration; public registration login and new-registration workflow; reuse note: Service workflow terms; login or form access does not imply scraping permission.
• Eswatini Trade Information Portal company name search procedure – Eswatini Trade Information Portal; public procedure page describing the company-name search route; reuse note: Portal publication terms and procedure-page attribution.
• ESPPRA – Eswatini Public Procurement Regulatory Agency; public procurement authority portal and notices; reuse note: Procurement-publication rules and ESPPRA site terms.
• Eswatini Revenue Service – Eswatini Revenue Service; public tax-service, registration and guidance portal; reuse note: Tax confidentiality, ERS site terms and purpose-limited public guidance.
• Central Statistics Office – Eswatini Government – Central Statistics Office; public government statistics office page and reports; reuse note: Government publication terms and report-specific attribution.
• Central Bank of Eswatini – Central Bank of Eswatini; public central-bank portal and publications; reuse note: Central-bank publication terms and financial-regulation limits.
• Central Bank of Eswatini bank supervision – Central Bank of Eswatini banking supervision; public bank-supervision page; reuse note: Central-bank publication terms and supervisory-use limits.
• Financial Services Regulatory Authority Eswatini – Financial Services Regulatory Authority; public non-bank financial services regulator portal and licensed-entity navigation; reuse note: FSRA site terms and financial-services regulatory limits.
• Eswatini Stock Exchange listed securities – Eswatini Stock Exchange; public listed-securities page; reuse note: Exchange site terms, market-data terms and no-endorsement cautions.
• GLEIF LEI records for Eswatini – Global Legal Entity Identifier Foundation; public LEI API and downloadable reference data; reuse note: GLEIF open data licence.