CVR API

Name: CVR API API
Brand: CVR API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey2 EndpointsREST

For Agents

Look up Danish (CVR) and Norwegian companies by registration number, P-number, name, or phone number to fetch official registry data.

Quickstart

Get started with CVR API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"look up a Danish company by CVR number"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CVR API API.

Look up a Danish company by its CVR number via GET /api?country=dk&vat={vat}

Look up a production unit (P-number) inside the Danish CVR via GET /api?country=dk&produ={produ}

Search Danish companies by name or partial name via GET /api?country=dk&search={search}

Resolve a Danish company from a phone number via GET /api?country=dk&phone={phone}

GET STARTED

Start building with CVR API API

Explore with Jentic

View OpenAPI Document

Use for: Look up a Danish company by CVR number, Find a Norwegian company by its organisation number, Search Danish companies by partial name, Resolve a company name from a phone number on a Danish caller

Not supported: Does not handle global company data, financial statements, or person-level enrichment - use for Danish (CVR) and Norwegian company-registry lookups only.

Jentic publishes the only available OpenAPI document for CVR API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for CVR API, keeping it validated and agent-ready. CVR API exposes the Danish Central Business Register (CVR) and adds a Norwegian company lookup, so applications can resolve a company by CVR/organisation number, P-number, name, or phone number. The two endpoints (GET and POST) accept the same query parameters and return company facts including registered address, industry code, status, and ownership. The token is passed as a query-string parameter and the API is widely used for KYC, due diligence, and B2B prospect enrichment.

Use Cases

Patterns agents use CVR API API for, with concrete tasks.

★ KYC for Danish B2B onboarding

Validate a CVR number a customer types into a signup form. The CVR API returns the registered company name, address, industry code, and active/dissolved status, which lets onboarding code auto-fill the rest of the form and reject inactive entities. The full check is one HTTP call.

Look up CVR 12345678 in Denmark and confirm the status is 'Active' before creating the customer account.

B2B prospect enrichment

Enrich a list of Danish or Norwegian companies with registry data before passing them into a CRM. A script iterates the source list, calls /api with the CVR or organisation number, and writes the standardised name, address, and industry back to the prospect record so sales reps see consistent data.

For each row in prospects.csv, call /api with the CVR number and append registered address and industry code to the row.

Caller-ID enrichment for inbound support

Resolve a Danish phone number to a registered company on inbound calls. The /api endpoint accepts a phone parameter and returns matching CVR records, which a CTI integration can use to surface the caller's company alongside the phone number in the agent console.

Look up phone +4533123456 and surface the matched company name and CVR number to the support agent.

Agent-driven CVR lookup via Jentic

Let an autonomous agent answer questions like 'Is this CVR number valid?' or 'Who is this Danish company?' inside a chat workflow. The agent searches Jentic for 'look up a Danish company by CVR number', loads the schema, and calls /api - the token never leaves the Jentic vault.

Through Jentic, look up CVR 12345678 and return the company name, address, and active status to the user.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for cvr api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api

Look up a company by CVR/organisation number, P-number, name, or phone (query string)

POST

/api

Same lookup as GET but with parameters in the request body

GET

/api

Look up a company by CVR/organisation number, P-number, name, or phone (query string)

POST

/api

Same lookup as GET but with parameters in the request body

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The CVR API token is stored encrypted in the Jentic vault. Jentic injects it at execution time so the raw token never lands in the agent's prompt or logs, even though the API normally takes the token as a query parameter.

Intent-based discovery

Agents search by intent (e.g. 'look up a Danish company by CVR number') and Jentic returns the CVR /api operation with its parameter schema, so the call is one step from intent to execution.

Time to first call

Direct CVR integration: a couple of hours for HTTP plumbing, query-token handling, and result parsing. Through Jentic: under 10 minutes - search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Clearbit

Global B2B company and contact enrichment

Choose Clearbit for global firmographic enrichment; pick CVR when you specifically need authoritative Danish or Norwegian registry data.

Alternative

People Data Labs

Global company and person dataset for enrichment and search

Use People Data Labs when global coverage matters and slight staleness is fine; CVR is right when you need the official Danish CVR record.

Alternative

FullContact

Identity resolution and contact enrichment platform

Pick FullContact when you need person-level identity resolution; CVR specifically resolves official Danish and Norwegian company entities.

FAQs

Specific to using CVR API API through Jentic.

Why is there no official OpenAPI spec for CVR API?

CVR API (cvrapi.dk) does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CVR via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the CVR API use?

A token passed as the 'token' query-string parameter. Through Jentic, the token is held in the encrypted vault and injected at execution time, so it never appears in agent prompts or logs.

Which countries does this CVR API cover?

Denmark and Norway. Pass country=dk for Danish CVR lookups and country=no for Norwegian organisation-number lookups against /api.

Can I look up a company by phone number?

Yes for Denmark. /api accepts a 'phone' query parameter alongside country=dk and returns the registered Danish company that matches the number.

What are the rate limits for the CVR API?

Limits depend on your cvrapi.dk plan rather than being declared in the spec. Free tiers are tightly throttled, so handle 429 responses with backoff and check your plan in the cvrapi.dk dashboard before running a bulk enrichment job.

How do I look up a Danish company through Jentic?

Run pip install jentic, search for 'look up a Danish company by CVR number', load the GET /api schema, and execute with country=dk and the CVR number. Jentic returns the registry response without exposing the token to the agent.