DAWA closes permanently on 17 August 2026. Every call to dawa.aws.dk will fail that day. Use this checklist to migrate your integration to Danadresse before the deadline — leave your email and we'll send you a printable PDF version.
Get the PDF checklist (+ migration tips by email)
No spam. One email with the checklist PDF and DAWA deadline reminders.
By subscribing you accept our privacy policy. Unsubscribe at any time.
Go through each step in order. Tick it off when done. Total estimated time: 30–60 minutes for a typical integration.
Search for dawa.aws.dk, api.dataforsyningen.dk and /autocomplete, /adresser, /datavask in your code. List every file and config that references DAWA.
grep -r "dawa.aws.dk\|dataforsyningen.dk" ./src
Sign up at danadresse.dk/dashboard/signup — no credit card. You get a key prefixed dawa_live_… within 30 seconds.
Replace https://dawa.aws.dk (or https://api.dataforsyningen.dk) with https://api.danadresse.dk. Do this in a single constant or environment variable — not scattered across the codebase.
Add X-Api-Key: dawa_live_… to your HTTP client's default headers. Alternatively use ?api_key=… as a query parameter for browser-side requests.
curl -H 'X-Api-Key: dawa_live_…' 'https://api.danadresse.dk/autocomplete?q=Rådhuspladsen'
Call /autocomplete?q=Rådhuspladsen&per_side=5 against Danadresse and compare the response structure to DAWA. Verify that tekst, adresse.id and adressebetegnelse fields are present and identical.
Look up a known address UUID via /adresser/{id}. Confirm that id, kvhx, etage, dør, adgangsadresse and all nested fields match DAWA's response exactly.
Send a fuzzy / dirty address string to /datavask/adresser?betegnelse=Rådhuspladsen+1+Kbh. Verify the kategori and resultater[0].adresse.id fields — these are the most commonly parsed values downstream.
If your integration uses format=geojson or accesses adgangspunkt.koordinater, verify the geometry type and coordinate order (longitude, latitude — GeoJSON standard) are preserved.
Update any domain-specific error alerts that reference dawa.aws.dk. Adjust your uptime monitors, Datadog / Grafana checks, and alert thresholds to point to the new domain.
Deploy to production. If you had a fallback to dawa.aws.dk during testing, remove it now. Monitor your API dashboard for the first 24 hours — error rate should stay at 0%.
Every type of product that uses DAWA is affected. Here's what each scenario looks like after migration.
Checkout address autocomplete keeps working. WooCommerce, Shopify, DanDomain — change the API base URL in the plugin settings and add the key. No code changes needed in most plugins.
Customer address validation at onboarding continues without interruption. Salesforce / HubSpot integration configurations typically have a single endpoint setting — update that and you're done.
Municipal self-service and health platforms using address lookup by CPR or parcel work identically. Response UUIDs match DAR — your database foreign keys are not affected.
Geocoding delivery points and ETA calculation: the adgangspunkt.koordinater field is preserved 1:1. GeoJSON output format is also identical. Route optimisation pipelines work unchanged.
If you sync DAWA events via /replikering/haendelser and /replikering/senesteSekvensnummer, these endpoints are fully supported — same shape, same sequence numbering. Your sync job needs only a base URL change.
Building data (BBR), administrative areas (DAGI), parishes, and regions are all available. Our /enrich endpoint adds BBR + DAGI + energy label + matrikel data on top of any address — useful for insurance, estate, and planning applications.
Get a free API key, run through the checklist, and go live before 17 August 2026. Takes under an hour for most integrations.
Get a free key → Read the full migration guide →Most integrations are done in under 30 minutes. The checklist above covers the most common setups. Complex replication pipelines or multi-tenant systems may take up to a day — but the code changes are still minimal.
No. We use the same UUIDs from DAR (the Danish Address Register). DAWA's id is identical to our id. No database migration required on your side.
Free plan: 1,000 calls/month per IP (no key required). Hobby plan: 2,000 calls/month with a free key. For production usage, Pro (89 DKK/mo) gives 300,000 calls/month with overage billing. Enterprise: unlimited with SLA.
Yes. Use a dawa_test_… key (issued from your dashboard) to hit sandbox mode. Test keys do not count towards your monthly quota and return realistic data.