Libraries
Three libraries: the widget at version 1.2.0, the JavaScript client and the .NET SDK at
1.2.0. Each keeps DAWA's paths, parameters, field names and ids, so records read the same as DAWA's
did. In each, suggestions are free and each address picked is one look-up: the widget does it for
you, and the clients ask for text-only suggestions with kun_tekst.
| Library | Package | For |
|---|---|---|
| JavaScript Autocomplete | npm getaddress-dk-autocomplete, or a <script> tag |
Address autocomplete on any text input, with a domain token: free suggestions, one look-up per address picked. Or use DAWA's open-source dawa-autocomplete2 with its baseUrl pointed at us. |
| JavaScript Client | npm getaddress-dk-api |
Every endpoint from Node 18+ or the browser, with TypeScript types. |
| .NET SDK | NuGet getAddress.Dk.Sdk |
Every endpoint from .NET Standard 2.0 or .NET 8, as a typed HttpClient. |
On your server, pass your API key. In a web page, pass a domain token instead: the API refuses an API key sent from a browser.
For an address field in the browser there are two widgets, both supported: ours,
getaddress-dk-autocomplete (getaddress.dk's defaults, the token as an
argument, styles included), or DAWA's open-source
dawa-autocomplete2
(npm) with its
baseUrl set to https://api.getaddress.dk/t/{your-domain-token}. Both call select with
the same object, so one handler works for either. Ours asks for free suggestions and pays one look-up per address
picked; dawa-autocomplete2 as published asks for DAWA's full answers, one look-up each once they suggest addresses. See
Two widgets, both supported.
Anything else: the API is plain HTTPS. See the resource pages for requests and responses, and the OpenAPI document to generate a client.