# Denmark Company Registry Scraper — CVR & Production Units (`foxlabs/denmark-company-data`) Actor

Official Danish company data from the Central Business Register: CVR number, legal form, status, industry code, employees, address, phone and production units.

- **URL**: https://apify.com/foxlabs/denmark-company-data.md
- **Developed by:** [Berkan Kaplan](https://apify.com/foxlabs) (community)
- **Categories:** Business, Lead generation
- **Features:** Limited permissions
- **Stats:** 13 total users, 6 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 company records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

<p align="center"><a href="https://apify.com/foxlabs/denmark-company-data"><img src="https://data.foxlabs.com.tr/img/denmark-company-data-banner.svg" alt="Denmark Company Data — CVR Business Register" width="100%" /></a></p>

## Denmark Company Data — CVR Business Register 🇩🇰

**foXLabs European company-registry series:** [UK](https://apify.com/foxlabs/uk-company-data) · [France](https://apify.com/foxlabs/france-company-data) · [Estonia](https://apify.com/foxlabs/estonia-company-data) · [Latvia](https://apify.com/foxlabs/latvia-company-data) · [Czechia](https://apify.com/foxlabs/czech-company-data) · [Poland](https://apify.com/foxlabs/poland-company-data) · [Slovakia](https://apify.com/foxlabs/slovakia-company-data) · [Slovenia](https://apify.com/foxlabs/slovenia-company-data) · [Norway](https://apify.com/foxlabs/norway-company-data) · [Finland](https://apify.com/foxlabs/finland-company-data)

🎉 Turn the Danish CVR register into clean, structured company data — no login, no API key, one row per entity, with employees, industry, phone, officers and production units.
Built for B2B sales, lead generation, KYB / compliance and market-research teams.

### 🔍 What is the Denmark Company Data — and when should you use it?

Give this actor company names or Danish CVR numbers and it returns matching companies from the Danish Central Business Register (CVR, via cvrapi.dk) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run queries the source live, so the data is as fresh as the registry itself.

**Use it when you need:** a Denmark company list for outreach; formation / status monitoring; or a canonical registry record for KYB and due diligence.

**Use something else when:** you need firmographics the registry doesn’t hold (revenue, headcount, website, email) — pair this with an enrichment actor from [Fox Labs](https://apify.com/foxlabs).

### 🤖 Use with AI agents

**Already on the Apify MCP server?** Ask for this Actor by name: `foxlabs/denmark-company-data`.

**Your agent can pay for its own runs.** This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over **x402 (USDC on Base)** or **Skyfire** — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

```
I want to pull Denmark company records using the Apify Actor `foxlabs/denmark-company-data`.
Input: `queries` is a list of company names or Danish CVR numbers. `maxResultsPerQuery` caps rows per query.
Start with: {"queries":["32345794","Novo Nordisk"],"maxResultsPerQuery":50}
Ask me what to look up, run the Actor, then summarise the rows as a table.
```

The machine-readable API, MCP config and OpenAPI definition live at `apify.com/foxlabs/denmark-company-data.md`.

### 📋 Overview

Everything you need to turn the Danish Central Business Register (CVR, via cvrapi.dk) into clean, structured data — in one actor, with no login, cookies or API key.

**Why teams pick this actor:**

- ✅ **Whole registry, one call** — name or ID in, matching companies out.
- 🧹 **No empty-promise columns** — only fields this registry actually fills; degenerate columns are removed.
- 🔗 **Stable join key** — `registrationNumber` ties rows across runs and to other Fox Labs actors.
- 💰 **Pay only for results** — per-row pricing, empty/failed lookups never billed.
- 🤖 **Agent-ready** — MCP + x402 agentic payments.

### ✨ Features

- 🔍 **Name or ID lookup** — relevance-ranked name search or exact registry-ID lookup.
- 🏢 **Full entity profile** — status, legal form, formation date, address and the registry’s own contact fields.
- 🧹 **Clean schema** — deduplicated camelCase rows, ready for CSV/Excel/JSON.

### 🎬 Quick Start

```bash
curl -X POST "https://api.apify.com/v2/acts/foxlabs~denmark-company-data/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["32345794","Novo Nordisk"],"maxResultsPerQuery":50}'
```

### 🚀 Getting Started (3 steps)

1. **Choose your targets** — company names or Danish CVR numbers.
2. **Set the cap** — `maxResultsPerQuery` limits rows per query.
3. **Run and export** — get a clean dataset as JSON, CSV or Excel.

### 📥 Input

```json
{"queries":["32345794","Novo Nordisk"],"maxResultsPerQuery":50}
```

| Field | Type | Description |
|---|---|---|
| `queries` | array | Company names or Danish CVR numbers. |
| `maxResultsPerQuery` | integer | Caps rows per query. |
| `maxConcurrency` | integer | How many queries to fetch at once. |
| `includeRaw` | boolean | Attach the source’s untouched record under `raw`. |

### 📤 Output

One row per company, saved to the dataset. Every row also carries `query`, `scrapedAt`, and — when a lookup fails — an `error` explaining why (never silently dropped, never billed).

| Field | Description |
|---|---|
| `country` | Country |
| `registry` | Registry |
| `companyName` | Company / entity name |
| `registrationNumber` | Registry ID — the join key |
| `taxNumber` | Tax identifier |
| `status` | `active` / `inactive` / `dissolved` |
| `statusRaw` | Status exactly as the registry words it |
| `legalForm` | Legal form / entity type |
| `incorporatedOn` | Formation / registration date (ISO) |
| `dissolvedOn` | Dissolution date where applicable (ISO) |
| `address` | Principal address |
| `city` | City |
| `postalCode` | Postal code |
| `countryName` | Country |
| `industry` | Primary industry (NACE) |
| `industryCode` | Primary industry code (NACE) |
| `employees` | Registered employee count |
| `capital` | Registered share capital |
| `website` | Website |
| `email` | Email |
| `phone` | Phone |
| `officers` | Officers |
| `sourceUrl` | Public registry URL for the record |
| `legalFormCode` | Legal-form code |
| `isBankrupt` | Is Bankrupt |
| `protectedAddress` | Protected Address |
| `productionUnitCount` | Production Unit Count |
| `productionUnits` | Production Units |

### 💼 Use cases

**1. Denmark firmographic enrichment** — attach employees, industry and phone to Danish companies.
*Input:* CVR numbers or names. *Output:* the full firmographic record. *Use:* enrich a CRM or lead list.

**2. Denmark B2B lead lists** — active Danish companies with industry + contact.
*Input:* name searches. *Output:* entities + phone + industry. *Use:* a ready sales list.

**3. KYB / due diligence** — verify a Danish company and its bankruptcy status.
*Input:* the CVR or name. *Output:* the canonical CVR record. *Use:* confirm status and standing.

### 🔗 Integration

**JavaScript / Node.js**

```javascript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/denmark-company-data').call({"queries":["32345794","Novo Nordisk"],"maxResultsPerQuery":50});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);
```

**Python**

```python
from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/denmark-company-data').call(run_input={"queries":["32345794","Novo Nordisk"],"maxResultsPerQuery":50})
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)
```

Written for `apify-client` 3 for Python, where `call()` returns a run object; with version 1 or 2 it returns a dict — write `run['defaultDatasetId']` there.

**Automation (n8n / Zapier / Make):** schedule or webhook → HTTP request to the actor API with your `queries` → handle the JSON dataset → push to a sheet, CRM or dashboard.

### 📊 Pricing

Pay-per-event: **per delivered record**. Empty or failed lookups are never billed. [View current pricing.](https://apify.com/foxlabs/denmark-company-data)

### ❓ FAQ

**Do I need an account, login or API key?** No. This reads the Danish Central Business Register (CVR, via cvrapi.dk).

**What do I search by?** Company names or Danish CVR numbers.

**How current is the data?** Every run queries the source live, so results are as fresh as the registry.

**Why are firmographics like revenue or website missing?** A public business registry doesn’t hold them; we don’t ship empty columns. Pair with an enrichment actor from Fox Labs.

**Can I export to CSV / Excel / JSON?** Yes — directly from the Apify dataset.

### 🐛 Troubleshooting

- **Fewer rows than expected** — raise `maxResultsPerQuery`, or refine the name.
- **A name returns an unexpected entity** — it matched a similar registered name; search the exact registry ID.
- **No rows for a name** — try the entity’s exact legal name or its registry ID.

### ⚖️ Is it legal to scrape this data?

This actor reads a public government business registry published as open data. Results can still contain personal data (e.g. a registered agent’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

### 🤝 Support & contact

- 🌐 **Website:** [data.foxlabs.com.tr](https://data.foxlabs.com.tr)
- 📧 **Email:** info@foxlabs.com.tr
- 🐛 **Issues:** open a ticket in the Actor’s **Issues** tab
- 🧰 **More clean B2B data actors:** [Fox Labs on Apify](https://apify.com/foxlabs)

### Changelog

#### 0.1.12 — 2026-10-08 — README: the Python example works with the current Apify client

- The README's Python example read the results with `run['defaultDatasetId']`. With the current Apify client for Python (version 3) `call()` returns a run object, not a dict, and that line raised `TypeError: 'Run' object is not subscriptable` — after the run itself had finished. The example now reads `run.default_dataset_id`; with client version 1 or 2, keep `run['defaultDatasetId']`. Checked with apify-client 3.2.1, 2.5.1 and 1.12.2.
- No code, output field or pricing change.

#### 0.1 — 2026-09-07

- **Fixed the outage.** cvrapi.dk returned `QUOTA_EXCEEDED` on every request because the User-Agent did not match the gateway's required `App - Provider - Contact` format, so the actor returned zero results. Updated the User-Agent; it now returns full company data again — name, VAT, address, industry, **employees, phone, officers, production units**.
- **README rebuilt to the full standard** (AI-agents + x402 + MCP, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

# Changelog

This Actor's version history is a separate document: https://apify.com/foxlabs/denmark-company-data/changelog.md

# Actor input Schema

## `queries` (type: `array`):

Danish CVR numbers (8 digits, e.g. `32345794`) or company names (`Maersk`).

## `maxResultsPerQuery` (type: `integer`):

When a query is a name rather than an exact identifier, how many matching companies to return.

## `includeRaw` (type: `boolean`):

Attach the register's untouched response under `raw`. Useful when you need a field this actor does not map.

## `requestDelayMs` (type: `integer`):

Politeness delay against a public register. Raise it for large runs.

## `proxyConfiguration` (type: `object`):

Optional, but helps spread requests on larger runs.

## Actor input object example

```json
{
  "queries": [
    "32345794",
    "Novo Nordisk",
    "Zendesk"
  ],
  "maxResultsPerQuery": 5,
  "includeRaw": false,
  "requestDelayMs": 200,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "queries": [
        "32345794",
        "Novo Nordisk",
        "Zendesk"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("foxlabs/denmark-company-data").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "queries": [
        "32345794",
        "Novo Nordisk",
        "Zendesk",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("foxlabs/denmark-company-data").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "queries": [
    "32345794",
    "Novo Nordisk",
    "Zendesk"
  ]
}' |
apify call foxlabs/denmark-company-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,foxlabs/denmark-company-data"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/AeWIsZcrTcp2oWDGz/builds/7DJZr7MHut0bvYbAK/openapi.json