PHONE_BLOCK_NOT_FOUND
No number block matches that country and prefix
GET /api/v1/phone/block/{country}/{prefix} found nothing to report: either no numbering plan Spaw syncs covers the country, or no block in it starts with the prefix. Nothing is charged.
- http status
- 404
- credits
- Nothing is billed for a failed request.
What it means
The block report is read from the regulators' own allocation tables, which Spaw syncs per country. A country whose regulator publishes no such table — or one whose numbers are filed under another region's table, as the Crown dependencies are under GB — has no rows of its own and answers this code.
A covered country answers it when the prefix simply is not in the plan: the digits are longer than any block, or they name a range the regulator has never opened. Validating a single number is unaffected; it works from the same tables and answers a verdict rather than this code.
What to do
Check the country is one whose numbering plan Spaw carries, and shorten the prefix to the area code itself — the report covers every block underneath it.
Example response
{
"success": false,
"error": {
"code": "PHONE_BLOCK_NOT_FOUND",
"message": "No number block in US starts with 999.",
"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
- All error codes
- Verdicts and the risk score
- API reference
markdown version: /docs/errors/PHONE_BLOCK_NOT_FOUND.md