Changelog · 2026-05-22

Nordic Data v0.5 — the canonical layer

Largest single release since launch. Expanded from Nordic-only to global with a new canonical layer.

What's new

New endpoints

• GET /v2/companies/{canonical_id} — full record with per-fact provenance
• GET /v2/companies/search?q=&country= — fuzzy name search (sub-200ms on 35M rows)
• GET /resolve/{scheme}/{id} — universal external-ID resolver
• GET /v2/companies/{id}/provenance — per-fact source + freshness
• GET /v2/companies/{id}/contacts — tiered confidence emails + phones
• GET /v2/companies/{id}/global-officers — cross-jurisdiction officer graph
• GET /v2/companies/{id}/related-by-domain — sister entities sharing a domain
• GET /sanctions/search — 1.6M dataset name search
• POST /sanctions/screen-bulk — bulk-100 names per call
• POST /companies/{id}/enrich — JIT enrichment for long-tail companies
• POST /gdpr/access and POST /gdpr/opt-out — self-serve GDPR
• GET /status.html — HTML status page with live KPIs

Zero breaking changes

The legacy /companies/{orgnr} endpoints work identically. Internally they resolve orgnr → canonical_id and return the same shape. Existing customer keys keep working.

Try it now

Sandbox key (no signup, 30 calls/hour, all features unlocked): sandbox_try_2026

curl -H "X-API-Key: sandbox_try_2026" \
  "https://api.nordicdata.cloud/v2/companies/search?q=equinor&country=NO&limit=3"

Interactive: /sandbox · Docs: /docs · Postman: /postman-collection.json · npm: npm install -g [email protected]

How we shipped it

The build itself was three days of autonomous agent work. Key engineering decisions documented in companion posts:

• Per-fact provenance — and what it cost to actually do this
• Cross-jurisdiction officer match — the KYB signal nobody surfaces