The error format (v1 vs. dawa)
1 min read
The error format
The error shape depends on the surface.
/v1/* (native):
JSON
{ "error": {
"type": "rate_limit_exceeded",
"message": "Du har overskredet dit forbrugsloft. Prøv igen senere.",
"code": 429,
"request_id": "req_ab12cd34",
"beskrivelse": { "da": "…", "en": "…" },
"doc_url": "https://docs.danskadresseapi.dk/?fane=v1&side=fejl-og-statuskoder",
"debug_url": "https://danskadresseapi.dk/dashboard/debug?req=req_ab12cd34" } }codeis the HTTP number (e.g. 429).typeis a string. Giverequest_idto support.- If you send
Accept-Language: en,messageis the standard English text for the type.
/dawa/* (DAWA shape):
JSON
{ "type": "ResourceNotFoundError",
"title": "The resource was not found",
"details": { "id": "0a3f50…" } }- Validation:
type: "QueryParameterFormatError",detailsis pair-arrays[["param","message"]]. - 401/403 are called
AuthorizationError, and 429 (both rate limit and quota) is calledTooManyRequestsError. Therequest_idis in theX-Request-IDheader.
Both surfaces keep theX-RateLimit-*andRetry-Afterheaders, so client-side back-off works the same.
Was this helpful?
