DAWA — Denmark's national address API, used by thousands of Danish websites, apps and systems — closed permanently on 1 October 2026 at 10:00 Danish time. Every integration that calls dawa.aws.dk or api.dataforsyningen.dk now gets 410 Gone. This guide explains what happened, what broke, and exactly how to fix it.
DAWA (Danmarks Adressers Web API) was the backbone of Danish address data from 2013. It provided a free, open REST API with 2.7 million Danish addresses, access addresses, postcodes, municipality codes, parishes, replication streams and geocoding. Virtually every Danish webshop, CRM, citizen portal and logistics system used it — usually without the developers even knowing, because it was bundled into a third-party plugin.
DAWA was operated by the Danish Agency for Data Supply and Efficiency (Styrelsen for Dataforsyning og Infrastruktur, SDFI) under the address register DAR. On 1 October 2026, the service was decommissioned in favour of the Datafordeler platform.
At 10:00 Danish time on 1 October 2026, all requests to the following domains started returning 410 Gone:
dawa.aws.dk — the original DAWA domainapi.dataforsyningen.dk — the newer alias (same service)This affects every endpoint: /autocomplete, /adresser, /adgangsadresser, /datavask, /postnumre, /vejnavne, /kommuner, /regioner, /sogne and /replikering. There was no grace period and there is no redirect — the service simply went dark.
Webshops: Address autocomplete in checkout. When customers can no longer type and select their address, conversion drops immediately. WooCommerce, Shopify, Magento, PrestaShop, DanDomain and Shoporama stores that use DAWA-based plugins are all affected.
CRM and sales systems: Address validation when creating contacts, leads or orders. Salesforce, HubSpot, Pipedrive and Dynamics 365 integrations that look up Danish addresses via DAWA now fail.
Citizen portals and public-sector apps: Self-service forms where citizens enter their address. From insurance claims to municipal applications — anything that validates or autocompletes against DAWA has stopped working.
Logistics and fleet: Driver apps and dispatch systems that geocode delivery addresses or look up the nearest address from GPS. The /adgangsadresser/reverse endpoint went offline too.
Replication subscribers: Companies that mirror the full Danish address dataset via /replikering/haendelser have received no updates since 1 October.
The official migration path is Datafordeler.dk — but it is not a drop-in for DAWA. The differences are significant:
For most DAWA users, migrating to Datafordeler directly means rewriting significant parts of their integration — weeks of work, not hours.
The simplest migration for existing DAWA users is a drop-in replacement: an API that serves the same endpoints, the same parameters and the same JSON shapes as DAWA — but runs independently on its own data from Datafordeler.
Danadresse is exactly this. It is a DAWA analog — the same REST interface, the same address UUIDs (from DAR), the same response format — with one difference: the base URL and an API key. You do not change your parsing code, your database schema or your data model.
Here are the three changes required:
Sign up at danadresse.dk/dashboard/signup. The free tier gives you 2,000 calls per month — enough for testing and low-volume production. No credit card required.
In your HTTP client, environment config or plugin settings, replace:
https://api.dataforsyningen.dk → https://api.danadresse.dk https://dawa.aws.dk → https://api.danadresse.dk
Add one header to every request:
X-Api-Key: dawa_live_…
Alternatively, pass it as a query parameter: ?api_key=dawa_live_… — useful for browser-side or JSONP integrations that can't set headers.
That's it. Your existing code — autocomplete UI, datavask pipeline, replication subscriber — works again, unchanged. The endpoints, parameters, HTTP methods and JSON response shapes are 1:1 with DAWA.
Use the 10-step migration checklist to verify each endpoint before you go live. The key tests:
/autocomplete?q=Rådhuspladsen and confirm the response array structure matches what your UI parser expects.id field on /adresser is the same DAR UUID as DAWA returns — your database foreign keys remain valid./datavask/adresser and confirm you receive a category A result with the same JSON fields./replikering/haendelser, confirm your sequence number is accepted and events are flowing.If your DAWA integration is inside a WooCommerce plugin, a Shopify app or a CRM module that you did not write, you have two options:
Danadresse includes the full DAWA surface — and adds a property data layer that DAWA never offered:
These are available via /api/v1/enrich/adresser/{id}/all and are especially useful for estate agencies, insurance platforms and property tech companies.
The shutdown was postponed once — from 1 July to 1 October 2026 — and then it happened on schedule, at 10:00. If anything of yours still calls DAWA, it is failing right now. The migration takes under 30 minutes for a simple integration; larger systems with many integrations, replication pipelines and third-party plugins need more time for testing and deployment. Start with the integrations your customers touch — checkout and sign-up forms first.