Switch from DAWA in 30 seconds

DAWA (dawa.aws.dk) closed on 1 October 2026 and now answers 410 Gone. Danadresse is a 1:1 replacement — same endpoints, same parameters, same JSON, same UUIDs.

Side by side

Compatibility matrix

All core DAWA endpoints work natively today — independent of DAWA, which is now closed.

Why is Danadresse a true drop-in?

• Same data source. We fetch directly from the Climate Data Agency's DAR — the same register DAWA uses. No third-party data.
• Same UUIDs. DAR's id_lokalId === DAWA's id. You do NOT need to migrate database references.
• Same JSON structure. Every response field has the same name, type and nesting as DAWA.
• Same query parameters. per_side, side, srid, struktur, fuzzy — all work.
• Same error envelope. 404 returns {"error":{"code","message"}}.

Example: cURL

# Before (DAWA)
curl 'https://dawa.aws.dk/autocomplete?q=Rådhuspladsen+1'

# After (Danadresse) — same JSON back
curl 'https://api.danadresse.dk/autocomplete?q=Rådhuspladsen+1' \
     -H 'X-Api-Key: dawa_live_…'

# Or with a query param instead of a header
curl 'https://api.danadresse.dk/autocomplete?q=Rådhuspladsen+1&api_key=dawa_live_…'

Example: WordPress / WooCommerce

We have a plugin that replaces the DAWA integration in one click. Install from GitHub or composer require danadresse/checkout.

DAWA's autocomplete widget (dawa-autocomplete2)

Used dawa-autocomplete2.min.js from dawa.aws.dk? We host the same library (v1.1.0, MIT) on the same path, pointed at our API. Change the host in the <script> tag and append your key — your dawaAutocomplete.dawaAutocomplete(…) code stays as it is.

<!-- Before (DAWA) -->
<script src="https://dawa.aws.dk/js/autocomplete/dawa-autocomplete2.min.js"></script>

<!-- After (Danadresse) -->
<script src="https://api.danadresse.dk/js/autocomplete/dawa-autocomplete2.min.js?key=dawa_live_…"></script>
<link rel="stylesheet" href="https://api.danadresse.dk/css/dawa-autocomplete2.css">

The key can also be passed as an option — dawaAutocomplete.dawaAutocomplete(input, { apiKey: 'dawa_live_…', select: … }) — or as params: { api_key: '…' }. Every DAWA option works: select, adgangsadresserOnly, fuzzy, params (e.g. { kommunekode: '101' }), minLength, multiline, id. Paths from cdn.dataforsyningen.dk/dawa/assets/dawa-autocomplete2/… work too — swap only the host. On a public website, lock the key to your domain(s) in the dashboard under API keys → Allowed domains — it then works for every visitor (no device binding) and only from your site.

Example: JavaScript SDK

npm install @danadresse/js
// dawa.js → danadresse.js
import { autocomplete } from '@danadresse/js';
const hits = await autocomplete('Rådhuspladsen 1');

Example: Python

pip install danadresse
# dawa-python → danadresse
from danadresse import Client
c = Client(api_key="dawa_live_…")
hits = c.autocomplete("Rådhuspladsen 1")

CLI migration tool

We built a CLI that scans your code for dawa.aws.dk references and suggests fixes:

npx @danadresse/migrate-cli scan ./src
npx @danadresse/migrate-cli rewrite ./src --apikey dawa_live_…

Security

• HTTPS only. HSTS preload, TLS 1.3.
• API keys are hashed. We store only SHA-256 + the last 4 digits — you see the key once at creation.
• Rate limit per key. Up to 360 calls/min on Hobby, 1,700/min on Basis, 7,000/min on Pro — no limit on Enterprise.
• EU data residency. All servers in the EU. No data leaves the EU.
• GDPR. Address data is public (CC BY 4.0). API logs pseudonymised after 30 days.

What happened on 1 October 2026?

DAWA closed and now answers 410 Gone. On Danadresse, for you: nothing. We run on our own data from Datafordeleren — address IDs stay the same. No code changes, no data migration.

Questions?

Email us at hello@lynbro.dk or open an issue on GitHub.

---

← Back to danadresse.dk

Privacy policy · Cookie policy · Terms · Cookie settings
LynBro ApS · Rødovre Parkvej 276, 2610 Rødovre · CVR 46321499 · info@lynbro.dk