A drop-in replacement for DAWA
DAWA closes on 1 October 2026 at 10:00. Every address surface it served has a Grundfast equivalent that is live in production today — same shape, same address identifiers, one new base URL and a bearer key.
The migration, in two lines
Change where the request goes and add a header. The rest of your integration can stay as it is.
# Before — DAWA, no key curl "https://api.dataforsyningen.dk/autocomplete?q=vesterbrogade+1" # After — Grundfast, bearer key, same idea curl -H "Authorization: Bearer gf_live_..." \ "https://api.grundfast.dk/v1/autocomplete?q=vesterbrogade+1"
DAWA surface → Grundfast /v1
Every row is live today and requires a gf_live_ key. A call without a key answers 401.
| DAWA | Grundfast |
|---|---|
/autocomplete | /v1/autocomplete/v1/adresse/search |
/adgangsadresser/{id}address by UUID | /v1/adresse/{uuid} |
/adgangsadresser/reverse | /v1/adgangsadresser/reverse |
/datavask/adgangsadressersingle or :batch | /v1/datavask/adgangsadresser/v1/datavask/adgangsadresser:batch |
/jordstykker + /jordstykker/reversecoordinate → BFE | /v1/jordstykker/v1/jordstykker/reverse |
/postnumrelist, lookup and autocomplete | /v1/postnumre/v1/postnumre/{nr}/v1/postnumre/autocomplete |
/vejnavnelist and autocomplete | /v1/vejnavne/v1/vejnavne/autocomplete |
/ejerlavlist, lookup and autocomplete | /v1/ejerlav/v1/ejerlav/{kode}/v1/ejerlav/autocomplete |
/kommuner /regioner /sogne /retskredse /politikredse /opstillingskredseone DAGI theme per lookup | /v1/dagi/{tema}/v1/dagi/{tema}/{kode} |
addresses on a propertydid not exist in DAWA | /v1/adgangsadresser/bfe/{bfe} |
What you gain by moving
A like-for-like swap is the floor, not the ceiling. DAWA stopped at the address.
- The property behind the address. The same lookup can carry BBR buildings and units, cadastral parcels and ejerlav, joined on the BFE number.
- Point-in-time reads.
?asOf=<date>and/historikreturn the address or property as it stood then. - Sets instead of loops.
:batchresolves many in one call, async export jobs deliver CSV, NDJSON or GeoJSON, and signed webhooks push changes instead of you polling.
Sources
The closing date has moved twice and both older dates are still circulating. Here is what the 1 October date rests on.
- Dataforsyningen: “Distribution af registre fra DAWA lukker” — updated 12 June 2026. The primary source for the current date.
- DAWA’s own documentation — the reference for the response shape the table above is held against.
Start before the shutdown
Every endpoint above is live now. Create a free key, repoint your base URL, and be done well before 1 October.
See also
Frequently asked questions
When exactly does DAWA close?
DAWA (Danmarks Adressers Web API) closes on 1 October 2026 at 10:00 Danish time. The date has moved twice — it was announced for 1 July 2026, then 17 August 2026 — so older articles and AI answers still quote the earlier dates. Klimadatastyrelsen confirmed the 1 October date on 12 June 2026.
What actually breaks on that date?
Anything calling dawa.aws.dk or api.dataforsyningen.dk should be assumed to stop responding. That includes address autocomplete in checkout forms, address washing, postal-code lookups and reverse geocoding.
How much of my integration has to change?
The base URL and authentication. Point requests at https://api.grundfast.dk/v1 and send an Authorization: Bearer gf_live_… header. DAWA was keyless; Grundfast requires a key and meters usage. Paths, query parameters and response shapes stay recognisable.
Do address UUIDs stay the same?
Yes. Both DAWA and Grundfast serve identifiers from DAR, the national address register, so stored address UUIDs keep resolving. You do not have to re-key your database.
Can I migrate before the shutdown?
Yes, and you should. Every endpoint in the table is live in production today and requires a gf_live_ key. There is no reason to wait for the deadline.
Address data originates from DAR via Datafordeler / SDFI and is licensed CC BY 4.0. Grundfast is an independent compatibility layer and is not affiliated with SDFI. More about Grundfast.