<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[GlobalEntity API Blog]]></title><description><![CDATA[GlobalEntity API Blog]]></description><link>https://globalentityapi.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 17:47:44 GMT</lastBuildDate><atom:link href="https://globalentityapi.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Get Danish company data (CVR) as JSON — and why the CVR number is the VAT number]]></title><description><![CDATA[If you work with Danish companies, you'll meet the CVR number fast — and one quirk saves a lot of confusion: In Denmark, a company's 8-digit CVR number is…]]></description><link>https://globalentityapi.hashnode.dev/get-danish-company-data-cvr-as-json-and-why-the-cvr-number-is-the-vat-number</link><guid isPermaLink="true">https://globalentityapi.hashnode.dev/get-danish-company-data-cvr-as-json-and-why-the-cvr-number-is-the-vat-number</guid><category><![CDATA[APIs]]></category><category><![CDATA[Denmark]]></category><category><![CDATA[kyc]]></category><dc:creator><![CDATA[Morten Ims]]></dc:creator><pubDate>Mon, 16 Nov 2026 22:24:18 GMT</pubDate><content:encoded><![CDATA[<p>If you work with Danish companies, you'll meet the <strong>CVR number</strong> fast — and one quirk saves a lot of confusion:</p>
<blockquote>
<p>In Denmark, a company's 8-digit <strong>CVR number is also its VAT (moms) number</strong>, just prefixed with <code>DK</code>. So CVR <code>24256790</code> → VAT <code>DK24256790</code>. One identifier, two jobs.</p>
</blockquote>
<p>Danish company data comes from <strong>CVR</strong> (Det Centrale Virksomhedsregister) via <strong>Virk</strong>, run by the Danish Business Authority. Here's how to pull it as clean JSON.</p>
<h2>One call</h2>
<pre><code class="language-bash">curl "https://www.globalentityapi.com/api/registry/search?country=Denmark&amp;q=Novo%20Nordisk" \
  -H "x-api-key: gea_live_…"
</code></pre>
<pre><code class="language-json">{
  "mode": "live",
  "country": "Denmark",
  "source": "cvr-virk",
  "results": [
    {
      "name": "NOVO NORDISK A/S",
      "orgNr": "24256790",
      "status": "Aktiv",
      "orgForm": "Aktieselskab",
      "industry": "Fremstilling af farmaceutiske præparater",
      "city": "Bagsværd"
    }
  ]
}
</code></pre>
<p>Look up directly by CVR number the same way — just pass it as <code>q</code>:</p>
<pre><code class="language-bash">curl "https://www.globalentityapi.com/api/registry/search?country=Denmark&amp;q=24256790" \
  -H "x-api-key: gea_live_…"
</code></pre>
<h2>Deriving the VAT number</h2>
<p>Because CVR = VAT, you can build the EU VAT ID with no extra call:</p>
<pre><code class="language-js">function cvrToVat(orgNr) {
  return "DK" + String(orgNr).replace(/\D/g, "");
}
// cvrToVat("24256790") -&gt; "DK24256790"
</code></pre>
<p>Then validate it against VIES if you need to confirm it's active for cross-border invoicing.</p>
<h2>What you get for a Danish company</h2>
<table>
<thead>
<tr>
<th>Field</th>
<th>Example</th>
</tr>
</thead>
<tbody><tr>
<td><code>name</code></td>
<td>NOVO NORDISK A/S</td>
</tr>
<tr>
<td><code>orgNr</code></td>
<td>24256790 (CVR = VAT)</td>
</tr>
<tr>
<td><code>orgForm</code></td>
<td>Aktieselskab (A/S)</td>
</tr>
<tr>
<td><code>status</code></td>
<td>Aktiv</td>
</tr>
<tr>
<td><code>industry</code></td>
<td>branchekode / NACE description</td>
</tr>
<tr>
<td><code>city</code></td>
<td>Bagsværd</td>
</tr>
</tbody></table>
<h2>Same call, every other country</h2>
<p>The value of a normalized layer is that Denmark isn't a special case in your code. Swap <code>country</code> and the shape stays identical:</p>
<pre><code class="language-bash">curl ".../api/registry/search?country=United%20Kingdom&amp;q=Tesco" -H "x-api-key: gea_live_…"
curl ".../api/registry/search?country=Germany&amp;q=SAP%20SE"        -H "x-api-key: gea_live_…"
</code></pre>
<p>66 registers across 30+ countries, one JSON schema. <a href="https://www.globalentityapi.com/cvr-api">Full details here</a>.</p>
<h2>Try it</h2>
<p>There's a live CVR demo (no signup) on the <a href="https://www.globalentityapi.com/cvr-api">CVR API page</a> — search Novo Nordisk, Maersk or Carlsberg. Keys come with a <a href="https://www.globalentityapi.com/">7-day free trial</a>, no card required.</p>
<p><em>Data comes live from CVR via Virk (</em><a href="http://data.virk.dk"><em>data.virk.dk</em></a><em>); attribution is retained on every record.</em></p>
]]></content:encoded></item><item><title><![CDATA[One API for every European company register (instead of sixty-six integrations)]]></title><description><![CDATA[If you've ever had to pull official company data for more than one country, you know the pain: every national business register is its own little world…]]></description><link>https://globalentityapi.hashnode.dev/one-api-for-every-european-company-register-instead-of-sixty-six-integrations</link><guid isPermaLink="true">https://globalentityapi.hashnode.dev/one-api-for-every-european-company-register-instead-of-sixty-six-integrations</guid><category><![CDATA[APIs]]></category><category><![CDATA[fintech]]></category><category><![CDATA[kyc]]></category><dc:creator><![CDATA[Morten Ims]]></dc:creator><pubDate>Mon, 16 Nov 2026 22:17:50 GMT</pubDate><content:encoded><![CDATA[<p>If you've ever had to pull <strong>official company data</strong> for more than one country, you know the pain: every national business register is its own little world.</p>
<ul>
<li>🇳🇴 Norway → <strong>Brønnøysund (BRREG)</strong> — great open API, Norwegian field names.</li>
<li>🇬🇧 UK → <strong>Companies House</strong> — REST, but its own auth and shapes.</li>
<li>🇩🇰 Denmark → <strong>CVR / Virk</strong> — where the CVR number is <em>also</em> the VAT number.</li>
<li>🇩🇪 Germany → <strong>Handelsregister</strong> — HRB numbers, registering courts, open data via OffeneRegister.</li>
<li>…and 30+ more, each different.</li>
</ul>
<p>Integrating each one means a new endpoint, a new data model, new auth, new edge cases — and ongoing maintenance every time a register changes. For a KYC/KYB or onboarding flow that needs pan-European coverage, that's dozens of separate integrations before you've shipped a feature.</p>
<h2>The "one schema" approach</h2>
<p>The fix is to put a <strong>normalization layer</strong> in front of all of them, so every register returns the same JSON. That's what <a href="https://www.globalentityapi.com/company-registry-api">GlobalEntity API</a> does — one REST endpoint, 66 registers across 30+ countries, one schema.</p>
<pre><code class="language-bash">curl "https://www.globalentityapi.com/api/registry/search?country=Norway&amp;q=Equinor" \
  -H "x-api-key: gea_live_…"
</code></pre>
<pre><code class="language-json">{
  "mode": "live",
  "country": "Norway",
  "source": "brreg",
  "results": [
    {
      "name": "EQUINOR ASA",
      "orgNr": "923609016",
      "status": "Active",
      "orgForm": "ASA",
      "city": "STAVANGER",
      "vat": true
    }
  ]
}
</code></pre>
<p>Want Germany instead? Change one query parameter:</p>
<pre><code class="language-bash">curl "https://www.globalentityapi.com/api/registry/search?country=Germany&amp;q=SAP%20SE" \
  -H "x-api-key: gea_live_…"
</code></pre>
<p>Same request shape, same response shape. Your parser doesn't care which country it is.</p>
<h2>A tiny multi-country client</h2>
<pre><code class="language-js">const COUNTRIES = ["Norway", "United Kingdom", "Denmark", "Germany"];

async function searchEverywhere(query, key) {
  const calls = COUNTRIES.map(async (country) =&gt; {
    const url = new URL("https://www.globalentityapi.com/api/registry/search");
    url.searchParams.set("country", country);
    url.searchParams.set("q", query);
    const res = await fetch(url, { headers: { "x-api-key": key } });
    const data = await res.json();
    return { country, results: data.results ?? [] };
  });
  return Promise.all(calls);
}
</code></pre>
<p>Because every country returns the same fields, you can merge, rank and display results without per-country branches.</p>
<h2>Where the data comes from</h2>
<p>Directly from official national registers and open-data sources (plus the GLEIF LEI index), each under its own licence, with attribution retained on every record. It's not a scrape — it's the authoritative source, normalized.</p>
<h2>When this is worth it</h2>
<ul>
<li><strong>KYC / KYB &amp; onboarding</strong> across multiple EU/EEA markets.</li>
<li><strong>Supplier / counterparty screening</strong> where you don't control which country a company is in.</li>
<li><strong>CRM / data enrichment</strong> — turn a company name into a verified legal entity with status, VAT and LEI.</li>
</ul>
<h2>Try it</h2>
<p>Each register has a live demo (no signup) — start on the <a href="https://www.globalentityapi.com/company-registry-api">hub page</a> and switch countries in the search box, or read the per-register guides for <a href="https://www.globalentityapi.com/companies-house-api">the UK</a>, <a href="https://www.globalentityapi.com/cvr-api">Denmark</a> and <a href="https://www.globalentityapi.com/handelsregister-api">Germany</a>. There's a <a href="https://www.globalentityapi.com/">7-day free trial</a>, no card required.</p>
]]></content:encoded></item></channel></rss>