DAWA migration · /adresser
DAWA adresser replacement — same /adresser, own data
DAWA's /adresser shuts down 17 August 2026. Danadresse serves the same endpoint with the same filters, struktur variants and GeoJSON — on its own, daily-updated data.
Looking up full addresses via DAWA's /adresser? Same endpoint, same filters (q, postnr, kommunekode, cirkel, polygon), same struktur (nestet/mini/flad) and the same GeoJSON output.
Before & after — one line changes
DAWA (closing 17 Aug 2026)
curl 'https://api.dataforsyningen.dk/adresser?postnr=1620&per_side=10'
Danadresse
curl 'https://api.danadresse.dk/adresser?postnr=1620&per_side=10' \
-H 'X-Api-Key: dawa_live_…'
Same path, same query parameters, same JSON response shape and the same DAR UUIDs — you only swap the host and add an X-Api-Key header.
What stays identical
Same filters
q, postnr, kommunekode, vejnavn, husnr, cirkel, polygon — unchanged.
Struktur variants
nestet (default), mini, flad — the same keys as DAWA.
Same UUIDs
DAR ids are identical — no database migration on your side.