ADDRESS_STREETS_NOT_FOUND
No street listing answers for that country or postcode
GET /api/v1/address/streets found nothing to report: either no address register Spaw syncs carries a street listing for the country, or the register lists no street at that postcode. Nothing is charged.
- http status
- 404
- credits
- Nothing is billed for a failed request.
What it means
The street listing is read from the national address registers Spaw syncs — every street each one lists inside each postcode, in the register's own spelling. A country with no such register, or one whose register was synced before its listing existed, has no streets to answer with and answers this code.
A covered country answers it when the register simply lists nothing at the postcode: the code is not in the register, or is one that holds no street addresses. Validating a single address is unaffected; it works from the same registers and answers a verdict rather than this code.
What to do
Check the country is one whose address register Spaw carries with a street listing, and that the postcode is a real one in that country's own notation.
Example response
{
"success": false,
"error": {
"code": "ADDRESS_STREETS_NOT_FOUND",
"message": "No street is listed at 9999 in CH.",
"request_id": "req_01m1kgdm4xngzmbmff68g94w0c"
}
}Every error carries the request_id also sent in the X-Request-Id header; quote it when writing to support.
Related
- NOT_FOUND · no such record on this account
- UNKNOWN_FEEDBACK_PROVIDER · the bounce webhook path names an unsupported provider
- ASN_NOT_FOUND · no autonomous system with that number is in the index
- PHONE_BLOCK_NOT_FOUND · no number block matches that country and prefix
- All error codes
- Verdicts and the risk score
- API reference
markdown version: /docs/errors/ADDRESS_STREETS_NOT_FOUND.md