v1 or /dawa — which should I choose?
DanskAdresseAPI gives you two entry points to the same Danish address data. For most people we recommend /dawa: a 100% compatible replacement for the official DAWA, so your code works unchanged — stable and predictable. v1 is our own API, which we are still building out. Here is the difference, and a clear recommendation.
The short answer
For most: choose /dawa. It is a 100% compatible drop-in replacement for the official DAWA — just change the base URL, keep all your code. Stable, fixed contract, with SLA and support.
Specifically need enrichment (BBR + DAGI in one call) or a modern JSON format? Then you can use v1 — our own API. Note that it is under active development.
What is /dawa?Recommended
The official DAWA (Denmark's addresses web API on dataforsyningen.dk) is widely used but being phased out. Our /dawa is an exact 1:1 replacement: same endpoints, same response format, same field names — even the same quirks. We mirror DAWA's contract exactly and monitor it around the clock against the real DAWA. It is the one we recommend for most.
Replace api.dataforsyningen.dk with api.danskadresseapi.dk/dawa. The rest of your code is unchanged — same paths (/adresser, /autocomplete, /adgangsadresser), same JSON.
We mirror DAWA's contract 1:1 and continuously verify against the real DAWA (conformance monitor every 5 minutes). You get DAWA's exact behaviour — with SLA, support and a stable future.
A fixed contract that does not change. Perfect if you have DAWA-based integrations, parsers or contracts — or just want something that behaves like DAWA, without surprises.
What is v1?
v1 is our own API, which we build and develop ourselves. It returns modern JSON in one flat format and can bundle enrichment (BBR + DAGI) in one call. It is usable today, but still under active development — so the surface expands and adjusts over time.
Add ?include=bbr,dagi to get building data (area, year built, usage) + administrative divisions (parish, police district, court district, region) alongside the address — no extra round-trips.
Predictable JSON with clear field names (data.betegnelse, wgs84, etc.) instead of DAWA's historical structure.
Autocomplete, address validation/cleansing, reverse geocoding, radius/bbox search, BBR and DAGI lookups, webhooks and batch — all under one key.
The differences side by side
| /dawa | v1 | |
|---|---|---|
| Purpose | Recommended — drop-in replacement for official DAWA | Our own API (under development) |
| DAWA compatibility | 100% compatible — change base URL only | Own format — requires adapting |
| Response format | Identical to DAWA (legacy format) | Clean, flat JSON (our design) |
| Endpoints | /dawa/adresser, /dawa/autocomplete, /dawa/adgangsadresser, /dawa/postnumre … | /v1/autocomplete, /v1/adresser, /v1/reverse, /v1/validate, /v1/bbr/*, /v1/dagi/* |
| Enrichment (BBR/DAGI) | No (like the official DAWA) | Yes — ?include=bbr,dagi in one call |
| Evolution | Fixed — frozen to DAWA's contract | Beta — changes & expands continuously |
| Best for | Most — existing DAWA code & stability | If you specifically want enrichment/modern format |
v1 is in beta — what does that mean?
v1 is usable today, but "beta" means we are actively developing and expanding it — new fields, new endpoints, adjustments. Changes are additive and backwards-compatible, but the surface grows over time. If you want something that is simply stable and 100% compatible from day one, /dawa is the safe choice.
How to choose
- You want something that behaves 100% like the official DAWA
- You have existing DAWA code — just change the base URL
- Stability and predictability matter most to you
- You are starting new and just want familiar, stable Danish address endpoints
- You want BBR and DAGI enrichment alongside the address in one call
- You prefer a modern, flat JSON format
- You are fine with the API being under active development
Yes. Both use the same account, same API key and same quota — you can use them side by side and switch at your own pace. Most build on /dawa for stability and compatibility, and use v1 in the specific places where they want enrichment.
Ready to get started?
Most start with /dawa — follow the drop-in guide and you are up and running in 30 seconds. Want enrichment? Explore v1.
Frequently asked questions
Which do you recommend?
For most we recommend /dawa, because it is 100% compatible with the official DAWA and has a fixed, stable contract — whether you are migrating existing code or starting new. v1 is our own API under active development; choose it if you specifically need enrichment or a modern format.
Do /dawa and v1 cost the same?
Yes. Calls count equally against your monthly quota whether they go to /v1 or /dawa — same key, same price.
Will /dawa keep working when the official DAWA shuts down?
Yes — that is exactly the point. /dawa is a standalone 100% compatible replacement with SLA and support, so your DAWA-based code can keep running unchanged.
Can I use both in the same app?
Yes. They share account, key and quota. Use /dawa as your foundation and v1 in the places where you want enrichment — at the same time.