Denmark Government Data Search

Search Danish public data across business, construction, health, legal, and procurement sources in one run.

• ✅ Search 24 Denmark-focused data products with one keyword list
• ✅ Cover business entities, StatBank statistics, planning data, health data, parliament records, EU legal material, and procurement
• ✅ Use it without coding, or connect it to ChatGPT, Claude, MCP, Make, Zapier, or n8n
• ✅ Enable only the categories you need so you do not scan irrelevant sources
• ✅ Free $5 Apify credit is enough to test real searches before you pay anything

Denmark public data is spread across several systems: Statistics Denmark, PlanData, Folketinget, ClinicalTrials.gov, WHO indicators, EUR-Lex, TED, and supporting aggregate products inside the SIP gateway. This Actor gives you one search layer across those Denmark-focused products, then returns structured records in a single dataset you can review, export, or feed into downstream workflows.

This Actor is best for discovery, topic scanning, monitoring, and early-stage research. It is not a substitute for deep source-by-source analysis, and it does not turn all Danish public data into one perfectly uniform database.

---

What you can do with it

1. Look up Danish companies, entities, and business signals

If you are researching companies active in Denmark, this Actor can search Denmark-focused business products in one run.

What you enter

• Search terms like Novo Nordisk, Maersk, Carlsberg, shipping, pharma
• Keep business enabled

What you get back

• GLEIF LEI entity matches for Denmark-related entities
• Statistics Denmark business statistics matches
• Business aggregate results from the SIP gateway

This is useful when you want a fast answer to questions like:

• Does this company appear in Denmark-focused entity data?
• Are there business statistics relevant to this industry?
• Which product should I inspect more deeply next?

2. Search Denmark construction, zoning, and property context

If your topic is development, housing, land use, or municipal planning, the construction category gives you a combined entry point.

What you enter

• Search terms like bolig, Copenhagen, industrial, zoning, housing
• Keep construction & property enabled

What you get back

• PlanData local plans
• PlanData building-zone or planning-area style records
• Statistics Denmark construction and property statistics
• Construction aggregate matches

This works well when you want a first-pass view of planning + property + construction context without manually checking multiple Danish portals.

3. Search Denmark health and clinical data

The health category is useful when you want Denmark-related health signals from multiple public-data products at once.

What you enter

• Search terms like diabetes, cancer, hospital, vaccination, mortality
• Keep health enabled

What you get back

• Denmark-related clinical trial records
• Statistics Denmark health and demographics tables
• Health expenditure data
• WHO indicator matches
• Health aggregate results

This is useful for healthcare research, public-health scanning, and early data discovery.

4. Monitor Denmark legal, parliament, and procurement signals

Legal and procurement are off by default, but they can be enabled when you want a broader public-sector scan.

What you enter

• Search terms like energy, healthcare, transport, public tender, directive
• Enable legal & parliament data and/or procurement & public finance

What you get back

• Folketinget parliament cases and votes
• EUR-Lex directives and regulations relevant to Denmark workflows
• TED procurement notices for Denmark-related procurement
• Statistics Denmark public-finance tables
• Procurement aggregate results

This is useful when you want to connect policy, legislation, and procurement in one search pass.

5. Connect Denmark public data discovery to AI or automation

This Actor works for manual use, but it is also meant to plug into broader workflows.

What you enter

• Search terms and category toggles in Apify
• Or the same parameters through API, MCP, or automation tools

What you get back

• Structured records in the dataset
• Stable SIP metadata fields such as _product_id, _source, _search_term, and _collected_at
• Output that is easy to export, summarize, monitor, or pass into spreadsheets and AI agents

This is the right pattern when you want search once, reuse everywhere.

---

How to use

You do not need to write code to use this Actor.

1. Open the Actor and click Try for free
2. Enter one or more search terms such as Novo Nordisk, København, bolig, or sundhed
3. Choose which categories to include:
   • business
   • construction & property
   • health
   • legal & parliament
   • procurement & public finance
4. Set max results per source
5. Run the Actor
6. Review the results in Apify or export them as JSON, CSV, Excel, XML, or RSS

By default, business, construction, and health are enabled. Legal and procurement are available when you want a broader scan.

---

What you get back

The Actor returns structured records from the selected Denmark-focused products. Exact fields vary a lot by source, because a LEI entity record, a StatBank statistical row, a parliament case, and a TED procurement notice are not the same kind of object.

Common SIP metadata fields include:

Field	What it means
_product_id	The SIP product that returned the record
_source	Human-readable source label
_search_term	The keyword that produced the record
_collected_at	UTC collection timestamp

In the Output tab, the default overview highlights fields such as:

• name
• type
• municipality
• value
• _source
• _search_term
• _collected_at

Depending on the enabled category, you may also see fields like:

• legal_name
• lei
• entity_status
• indicator
• period
• municipality
• plan_name
• status
• title
• committee
• buyer
• deadline

Here is a simplified example:

[
  {
    "legal_name": "Novo Nordisk A/S",
    "lei": "549300I6KHWHOQO2XR19",
    "entity_status": "ACTIVE",
    "_product_id": "dk_gleif_lei",
    "_source": "gleif_lei",
    "_search_term": "Novo Nordisk"
  },
  {
    "indicator": "Number of enterprises",
    "industry": "Water transport",
    "value": "245",
    "period": "2024",
    "_product_id": "dk_statbank_business_stats",
    "_source": "statbank_business_stats",
    "_search_term": "Maersk"
  }
]

The goal is not to force every Danish source into identical semantics. The goal is to make cross-source discovery fast enough to act on.

---

Coverage

This Actor currently searches 24 Denmark-focused data products across 5 categories:

Category	What is included	Count
Business	GLEIF LEI, StatBank business, business aggregate	3
Construction	PlanData zones and local plans, StatBank construction/property, construction aggregate	5
Health	Clinical trials, StatBank health/demographics/expenditure, WHO indicators, health aggregate	6
Legal	Folketinget cases and votes, EUR-Lex directives and regulations, legal aggregate	5
Procurement	TED procurement, StatBank government finance, municipal accounts, regional accounts, procurement aggregate	5

There is one important boundary to state clearly:

• These are 24 SIP data products, not 24 completely separate Danish institutions
• Some of the 24 are aggregate products that sit on top of narrower source products
• A search can therefore return both narrow source rows and broader aggregate rows depending on which categories are enabled

There is a second important boundary:

• Some products are record-style sources such as LEI entities, parliament cases, votes, or clinical trial entries
• Some are statistical or tabular sources such as StatBank and WHO indicators
• Some are public-sector discovery sources such as TED procurement or legal material from EUR-Lex

So the right mental model is: this Actor is a Denmark public-data discovery layer across multiple source types, not a single perfectly standardized Danish master database.

---

Pricing

This Actor is currently listed on Apify with pay-per-event pricing:

• $3.00 per 1,000 records returned

That is equivalent to about:

• $0.003 per record
• about 1,666 records for the free $5 Apify credit

In practice, your cost depends on how many results you return. You can control that with:

• category toggles
• number of search terms
• maxResultsPerSource

For the current pricing page, see:

• https://apify.com/lentic_clockss/denmark-data-search/pricing

---

Connect to your tools

You can use this Actor manually or connect it to your stack.

Tool	How to use it
Apify Console	Run it directly with a form input
Make.com	Use the Actor via Apify integration
Zapier / n8n	Trigger runs and send results into downstream workflows
ChatGPT / Claude	Connect through Apify MCP
Scripts / apps	Call it through the Apify API

If you want to use it with AI workflows, Apify MCP is usually the cleanest path.

---

When to use something else

This Actor is a strong fit when you want a broad Denmark public-data entry point across business, planning, health, legal, and procurement topics.

Choose something else if you already know you need a narrower or deeper workflow:

• Use a dedicated EU business actor if you need broader European company coverage rather than Denmark-focused discovery
• Use a dedicated financial-data actor if you need banking, monetary, or supervisory datasets rather than mixed government search
• Use a source-specific workflow if you need deep StatBank analysis, legal interpretation, or procurement operations
• Use a local domain-specific pipeline if you need highly curated municipal, sectoral, or case-management data

In short, this Actor is best for finding relevant Denmark public data quickly, not for replacing every source-specific analytical workflow.

---

FAQ

Q: Does this search all Danish government data?
A: No. It searches 24 Denmark-focused SIP products across 5 categories. That is broad coverage, but not the whole Danish public-data universe.

Q: Are all 24 sources completely different institutions?
A: No. The 24 count includes aggregate products as well as narrower source products.

Q: Does it support Danish search terms?
A: Yes. Danish terms work where the upstream product supports them. Some sources are more Denmark-native, while others like GLEIF or EUR-Lex can also respond well to English.

Q: Can I get municipality-level data?
A: In some categories, yes. For example, PlanData and some StatBank products can expose municipality-level context when those fields exist upstream.

Q: Can I export the results?
A: Yes. Apify datasets can be exported in formats like JSON, CSV, Excel, XML, and RSS.

Q: Is this only for developers?
A: No. It can be run directly in Apify with form inputs, and the developer-oriented examples are tucked into collapsible sections.

---

Related Actors

If you are building a broader European public-data workflow, these may also fit:

Need	Actor
EU business and company registries	EU Business Data Search
Switzerland public-sector data	Switzerland Government Data Search
France public-sector data	France Government Data Search
UK public-sector data	UK Government Data Search

More actors: apify.com/lentic_clockss

---

Also Available

• Direct API: https://opendata.best/api/v1/data
• Postman collection: Fork and test
• GitHub: Collection source files