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

Jordan has a serious official company-data ecosystem, but it should not be reduced to a simple list of companies. The right way to evaluate Jordan is to start with the official register, then add open-data, statistics, procurement, intellectual-property and regulator layers.

The strongest route is the opendata.gov.jo company dataset/API-guide page, JONEPS procurement, Central Bank of Jordan, Jordan Securities Commission and the Ministry of Industry, Trade and Supply; Companies Control Department, Department of Statistics and Amman Stock Exchange remain source-mapped but de-linked until bot-profile access is stable. That makes Jordan a Levant registry/open-data source map with CCD verification, official dataset/API-guide evidence and Arabic-English normalization caveats, but it does not remove the usual reuse checks: dataset terms, attribution, no-endorsement language, privacy, marketing-law boundaries and source freshness.

This guide maps the main official sources for company data in Jordan, explains what each source can and cannot do, and shows where a normalized CompaniesData-style dataset adds value.

The deeper question is not whether a source exists. The useful question is which source can be trusted for identity, which one proves events or filings, which one is usable at scale, which one is only a manual service, and which fields become legally sensitive once the data is reused commercially.

Quick Answer

Jordan is a strong controlled-access refresh candidate because the Companies Control Department is the company-registry authority, opendata.gov.jo provides a company dataset/API-guide signal, and procurement, statistics, central bank, securities, exchange and commerce-ministry sources add useful enrichment layers.

For practical work, the most useful source stack is: Companies Control Department, Jordan open-data company dataset, Jordan Online E-Procurement System, Department of Statistics Jordan, Central Bank of Jordan, Jordan Securities Commission.

The safe editorial answer is this: Jordan has strong public and official business-data sources, but public data is not automatically bulk-downloadable, marketing-ready or free of personal-data constraints.

A serious Jordan dataset normally needs at least four layers: the legal register for entity identity, official publications or filings for change events, public procurement/regulator/IP/statistical sources for enrichment, and a separate compliance layer for privacy, contact-data use, suppression and lawful outreach.

Key Takeaways

• Best starting point: the opendata.gov.jo company dataset/API-guide page, JONEPS procurement, Central Bank of Jordan, Jordan Securities Commission and the Ministry of Industry, Trade and Supply; Companies Control Department, Department of Statistics and Amman Stock Exchange remain source-mapped but de-linked until bot-profile access is stable.
• Core source stack: Companies Control Department, Jordan open-data company dataset, Jordan Online E-Procurement System, Department of Statistics Jordan, Central Bank of Jordan, Jordan Securities Commission.
• Reuse rule: public visibility is not the same as bulk reuse, resale permission or marketing-contact permission.
• Buyer value: the useful dataset is the normalized, deduplicated and source-auditable version, not a raw list of portal links.
• Commercial separation: official company records, enriched company profiles and business contact data should remain separate layers with separate compliance notes.

Editorial Methodology

This article uses an official-source-first method. Sources are included when they help verify legal existence, public filings, procurement activity, taxpayer or identifier context, IP ownership, regulated status, statistics or lawful compliance context. Commercial providers and contact-data products are not used as authority for official reuse rights.

• Prefer the national registry, company house, gazette or official business-registration authority before any secondary source.
• Classify access as search, API, bulk download, paid extract, subscription, document workflow, data catalogue or unclear/manual access.
• Separate legal-entity data from establishment statistics, procurement suppliers, listed-company disclosures, tax identifiers and private contact data.
• Treat beneficial owners, officers, addresses, signatures, insolvency notices and sole-trader records as privacy-sensitive unless the source and law clearly support reuse.
• Hold or omit unstable source links when live QA shows 403, 429, 5xx, DNS, TLS or timeout behaviour that would create broken-link noise.

What Counts as Company Data in Jordan?

In Jordan, these layers should not be collapsed into one undifferentiated database. A registry result may prove legal existence, a procurement notice may prove public-sector activity, an IP record may prove brand or invention ownership, and a regulator list may prove supervision. Those are different facts with different update cycles, identifiers and reuse boundaries.

Reuse Rights and Compliance

Across jurisdictions, public-sector-information and open-data policies can support reuse of public-sector data, and high-value dataset rules increasingly treat company and company-ownership data as important public information. In practice, Jordan's actual reuse position still depends on each source, endpoint, licence and access method.

• Cite official sources and preserve update dates where the source provides them.
• Do not imply that a derived dataset is endorsed by the registry or public authority.
• Do not mix public register data with marketing-contact permission.
• Check whether API, bulk download, paid extract and web-search access have different terms.
• Treat officers, beneficial owners and natural-person data as GDPR-sensitive where applicable.

Refresh as a controlled registry/open-data guide: CCD search/extract routes and the opendata.gov.jo company dataset/API-guide can support company-data verification and ingestion planning, but the article must not claim complete free open bulk coverage. Preserve Arabic-English normalization, privacy, marketing-contact and source-provenance caveats.

Coverage, Access and Update Risk

The most common mistake in Jordan company-data work is to confuse visibility with completeness. A public search screen can be authoritative for one entity lookup without being suitable for bulk ingestion. A downloadable dataset can be reusable for a defined snapshot while still excluding filings, documents, directors, inactive entities or historical changes.

• Coverage: identify whether the source covers companies, business names, branches, non-profits, sole traders, listed issuers, regulated entities or only a sector subset.
• Freshness: preserve the source update date and avoid mixing live portal results with old downloaded files without version labels.
• Identifiers: map registration numbers, tax identifiers, procurement supplier IDs, LEI records and exchange tickers as separate keys until verified.
• Language and formats: normalize local-language names, legal forms, transliteration, accents, abbreviations and address formats carefully.
• Operational access: document whether the workflow is public search, API, bulk file, paid extract, login-only service, PDF, CKAN/OData/SPARQL or manual request.

Reuse Checklist for Jordan

Resource Pack

Use this resource pack as a working map for verification, ingestion planning and source-risk review. The small source logos are decorative credibility cues only; the authority still comes from the official URL, owner, access model and reuse note.

Source-by-Source Deep Dives

1. Companies Control Department

Owner: official registry. Access: Companies Control Department.

• What it gives: Legal-entity registration, registry authority and company verification.
• Reuse value: CCD terms
• Main limitation: No complete free open-bulk proof; services and extracts may be controlled.

Companies Control Department is a official registry source for Jordan. Its main practical value is Legal-entity registration, registry authority and company verification. Access is through Companies Control Department, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: CCD terms. The main limitation is No complete free open-bulk proof; services and extracts may be controlled. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

2. Jordan open-data company dataset

Owner: official open data. Access: https://opendata.gov.jo/en/dataset/api_guide/companies-223-2019.

• What it gives: Open-data signal for company-data/API-guide context.
• Reuse value: Jordan open-data dataset terms
• Main limitation: Dataset freshness, fields and API mechanics must be checked before ingestion.

Jordan open-data company dataset is a official open data source for Jordan. Its main practical value is Open-data signal for company-data/API-guide context. Access is through https://opendata.gov.jo/en/dataset/api_guide/companies-223-2019, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: Jordan open-data dataset terms. The main limitation is Dataset freshness, fields and API mechanics must be checked before ingestion. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

3. Jordan Online E-Procurement System

Owner: official procurement. Access: https://www.joneps.gov.jo/.

• What it gives: Supplier, tender and public-contract enrichment.
• Reuse value: JONEPS terms
• Main limitation: Procurement subset only.

Jordan Online E-Procurement System is a official procurement source for Jordan. Its main practical value is Supplier, tender and public-contract enrichment. Access is through https://www.joneps.gov.jo/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: JONEPS terms. The main limitation is Procurement subset only. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

4. Department of Statistics Jordan

Owner: official statistics. Access: Department of Statistics Jordan.

• What it gives: Business and economic statistical context.
• Reuse value: DOS terms
• Main limitation: Aggregate layer, not company-level registry data.

Department of Statistics Jordan is a official statistics source for Jordan. Its main practical value is Business and economic statistical context. Access is through Department of Statistics Jordan, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: DOS terms. The main limitation is Aggregate layer, not company-level registry data. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

5. Central Bank of Jordan

Owner: regulator. Access: https://www.cbj.gov.jo/.

• What it gives: Financial-sector supervised-entity context.
• Reuse value: CBJ terms
• Main limitation: Sector-specific.

Central Bank of Jordan is a regulator source for Jordan. Its main practical value is Financial-sector supervised-entity context. Access is through https://www.cbj.gov.jo/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: CBJ terms. The main limitation is Sector-specific. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

6. Jordan Securities Commission

Owner: regulator. Access: https://www.jsc.gov.jo/.

• What it gives: Listed and regulated entity enrichment.
• Reuse value: JSC terms
• Main limitation: Regulated subset only.

Jordan Securities Commission is a regulator source for Jordan. Its main practical value is Listed and regulated entity enrichment. Access is through https://www.jsc.gov.jo/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: JSC terms. The main limitation is Regulated subset only. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

7. Amman Stock Exchange

Owner: official exchange. Access: Amman Stock Exchange.

• What it gives: Listed-company and issuer context.
• Reuse value: exchange terms
• Main limitation: Listed-company subset only.

Amman Stock Exchange is a official exchange source for Jordan. Its main practical value is Listed-company and issuer context. Access is through Amman Stock Exchange, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: exchange terms. The main limitation is Listed-company subset only. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

8. Ministry of Industry, Trade and Supply

Owner: official ministry. Access: https://www.mit.gov.jo/.

• What it gives: Commerce, trade and IP-adjacent authority context.
• Reuse value: ministry terms
• Main limitation: Authority/service layer, not a company master file.

Ministry of Industry, Trade and Supply is a official ministry source for Jordan. Its main practical value is Commerce, trade and IP-adjacent authority context. Access is through https://www.mit.gov.jo/, so the source should be treated according to that access model rather than assumed to be an unrestricted bulk feed.

For reuse, the working rule is: ministry terms. The main limitation is Authority/service layer, not a company master file. In a normalized company-data workflow this source should be captured with provenance, retrieval date, field-level caveats and a clear distinction between legal-entity facts, compliance signals and any later marketing/contact enrichment.

Held Source-Risk Findings

The following routes are useful research context but are not clean linked evidence in this article cycle:

• Companies Control Department: held and de-linked after the latest source-route check returned real browser content but empty or non-semantic content for Googlebot and Bingbot profiles. The opendata.gov.jo company dataset remains the clean linked CCD/open-data route for this pass.
• Department of Statistics Jordan: held and de-linked after Googlebot received an empty response while browser and Bingbot profiles retrieved real content. Use it as aggregate statistical context only until all profiles clear.
• Amman Stock Exchange: held and de-linked after the latest quality gate recorded HTTP 500 responses for Googlebot and Bingbot profiles. Jordan Securities Commission remains the clean linked securities-regulator source; the exchange route can return to the public source stack only after browser, Googlebot and Bingbot profiles all retrieve real issuer or market content without failure semantics.

Practical Options

Official open-data or API route

Start with the opendata.gov.jo company dataset/API-guide page for open-data/API planning, then enrich with JONEPS procurement, Central Bank regulated-entity context, Jordan Securities Commission disclosures and Ministry of Industry, Trade and Supply services. Treat direct Companies Control Department and Department of Statistics routes as held context until bot-profile access is stable. Keep direct Companies Control Department, Department of Statistics and Amman Stock Exchange routes as source-mapped context until Googlebot and Bingbot retrieve real source content again.

For production use, treat this route as an ingestion plan rather than a single download. Start with the official registry or data catalogue, keep raw source snapshots, record access terms, then add enrichment sources one by one with field-level provenance.

Manual verification and document route

Some countries expose important company facts through certificates, PDF filings, gazette notices, paid extracts or login-based services. Those sources can be valuable, but they should be documented as controlled workflows. Do not describe them as open APIs or bulk datasets unless the authority clearly publishes that access model.

Contact-data and marketing-list route

For sales outreach, company identity data is only the first layer. Business emails, phone numbers, contact roles, suppression logic and segmentation require a separate compliant contact-data process. That layer should be documented separately from official registry reuse.

Private reports and risk products

Private company-report providers can be useful for manual due diligence in Jordan, but the editorial focus here is not a directory of competitors. The strategic value is understanding which official sources exist and where normalization is required.

If a user needs CRM-ready company records, the practical path is to combine official-source provenance with enrichment, deduplication, quality checks and lawful delivery controls. That is different from buying a generic lead list: the official-source layer explains what can be verified, while the commercial dataset layer explains how the records can be used operationally.

What Is Missing from Official Open Data?

• Do not claim a complete free official bulk Jordan company register unless a current official dataset proves that exact scope and reuse right.
• CCD services, searches and extracts should be treated as controlled registry workflows, not unrestricted scraping targets.
• Arabic-English names, transliteration, legal-form labels and address components require careful normalization before matching or resale.
• Procurement, regulator, exchange, statistics and ministry sources are enrichment layers, not a universal legal-entity master file.
• Public registry, officer, address, procurement or regulated-entity records are not marketing-contact consent.
• Business emails, phone numbers and CRM-ready contact fields require a separate lawful contact-data workflow through CompaniesData.cloud.

This is why company-data products often add value even when the underlying public sources are strong: official data is frequently split across authorities, formats, languages, identifiers and access models.

Missing data should be treated explicitly in the dataset design. If an official source lacks bulk downloads, CompaniesData should not pretend that the bulk file exists; it should record the source limitation, add alternate official enrichment where lawful, and expose confidence fields so users know which attributes came from which layer.

Recommended Data Model

A practical CompaniesData-style model for Jordan should keep source evidence and commercial-use fields separate. The core table should hold legal entity identity, status, registration identifiers, legal form, jurisdiction, registered address and source dates. Separate enrichment tables can then store procurement awards, IP assets, regulator status, listed-company signals, LEI matches, sanctions/compliance hits and statistics-sector context.

• Entity identity: legal name, normalized name, registration number, jurisdiction, legal form and lifecycle status.
• Source provenance: source URL, authority, retrieval date, access method, licence/reuse note and confidence flag.
• Event history: incorporation, amendments, filings, gazette notices, insolvency or dissolution where legally public.
• Enrichment: procurement, IP, regulator, exchange, LEI and official statistics layers with their own source dates.
• Commercial delivery: CRM-ready exports, segmentation and contact-data fields only when a separate lawful basis and suppression workflow exist.

How CompaniesData Adds Value

For Jordan, CompaniesData's role is to turn fragmented source material into a usable business dataset: normalized company names, deduplicated entities, consistent country and activity fields, source provenance, update tracking and enrichment hooks.

• Normalize register identifiers and legal names.
• Match official company records with procurement, IP, LEI and regulator signals.
• Flag source provenance so every derived profile can be audited.
• Separate company identity from contact-data and marketing-permission layers.
• Package data for analysis, CRM enrichment and market research instead of forcing users to parse portals manually.

For Jordan, the editorial value of CompaniesData is not claiming that every record is open or that every field can be reused without conditions. The value is the opposite: making source boundaries visible, normalizing messy records, adding explainable enrichment and delivering a dataset that users can audit instead of a black-box scrape.

Request a CompaniesData sample for Jordan if you need a practical dataset rather than a list of source portals.

Source Matrix

Source	Owner	What it gives	Reuse value	Limitations
Companies Control Department	official registry	Legal-entity registration, registry authority and company verification.	CCD terms	No complete free open-bulk proof; services and extracts may be controlled.
Jordan open-data company dataset	official open data	Open-data signal for company-data/API-guide context.	Jordan open-data dataset terms	Dataset freshness, fields and API mechanics must be checked before ingestion.
Jordan Online E-Procurement System	official procurement	Supplier, tender and public-contract enrichment.	JONEPS terms	Procurement subset only.
Department of Statistics Jordan	official statistics	Business and economic statistical context.	DOS terms	Aggregate layer, not company-level registry data.
Central Bank of Jordan	regulator	Financial-sector supervised-entity context.	CBJ terms	Sector-specific.
Jordan Securities Commission	regulator	Listed and regulated entity enrichment.	JSC terms	Regulated subset only.
Amman Stock Exchange	official exchange	Listed-company and issuer context.	exchange terms	Listed-company subset only.
Ministry of Industry, Trade and Supply	official ministry	Commerce, trade and IP-adjacent authority context.	ministry terms	Authority/service layer, not a company master file.

Jordan has a credible official source stack for a deep refresh: Companies Control Department for registry authority, an official company dataset/API-guide route on opendata.gov.jo, JONEPS procurement, Department of Statistics context, Central Bank/JSC/Amman Stock Exchange regulated and listed-entity layers, and Ministry of Industry, Trade and Supply service context. The article should be precise about controlled services, no-complete-bulk claims and Arabic-English matching.

FAQ

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

Not always. Jordan has official company-data sources, but bulk access, API access, paid extracts and web search can be separate products. Do not assume a complete free bulk file unless the specific source proves it.

What is the best first source for Jordan company data?

The best first source is the opendata.gov.jo company dataset/API-guide page, JONEPS procurement, Central Bank of Jordan, Jordan Securities Commission and the Ministry of Industry, Trade and Supply; Companies Control Department, Department of Statistics and Amman Stock Exchange remain source-mapped but de-linked until bot-profile access is stable. It should then be combined with statistics, procurement, IP and regulator sources.

Can public company data be reused commercially?

Often yes, but only under the conditions of the specific source. Attribution, update-date preservation, no-endorsement wording and GDPR controls may apply.

Can I use registry data for cold email marketing?

No automatic conclusion follows from public registry access. Marketing requires a separate lawful basis, suppression handling and contact-data compliance review.

Why use CompaniesData instead of manually collecting Jordan sources?

Manual collection is slow because identifiers, formats, languages and coverage differ by source. CompaniesData adds normalization, matching, deduplication, provenance and practical delivery formats.

How often should Jordan company data be refreshed?

Refresh cadence depends on the source. Registry searches and APIs can support frequent checks, while gazettes, procurement portals, statistical releases and paid extracts may update on different schedules. A reliable dataset should store retrieval dates and source-specific update notes.

What should be audited before publishing or selling an enriched dataset?

Audit source authority, licence terms, personal-data exposure, contact-data lawful basis, field provenance, suppression rules, update dates and whether any official source prohibits automated reuse or resale.

Official Sources

• Companies Control Department – official registry
• Jordan open-data company dataset – official open data
• Jordan Online E-Procurement System – official procurement
• Department of Statistics Jordan – official statistics
• Central Bank of Jordan – regulator
• Jordan Securities Commission – regulator
• Amman Stock Exchange – official exchange
• Ministry of Industry, Trade and Supply – official ministry