bzst_rejected
BZSt returned an unrecognised status code that does not map to a typed vatverify error.
HTTP 400 · Bad Request
Example response
{
"error": {
"code": "bzst_rejected",
"message": "BZSt returned unrecognised status code: 9999.",
"retryable": false
},
"meta": {
"request_id": "a1b2c3d4-...",
"latency_ms": 890,
"bzst_status_code": "9999"
}
}What happened
BZSt responded with a status code that is not covered by vatverify's mapping of known eVatR codes. This is rare. It typically means either the BZSt API contract changed and introduced a new status code, or an edge case in the BZSt response was not anticipated in the current implementation.
The raw BZSt status code is always surfaced in meta.bzst_status_code so you can record it and report it.
How to fix
- Open a bug report with vatverify support, providing the
request_idand the value frommeta.bzst_status_code. This allows the unknown code to be mapped and a typed error added. - As a workaround, fall back to a plain
/v1/validatecall for the same VAT number. This queries VIES rather than BZSt and will confirm whether the number is currently registered, though it will not produce a §18e qualified confirmation. - Do not retry
bzst_rejectedautomatically. It is markedretryable: falsebecause a retry against BZSt will produce the same unrecognised status.
Related errors
bzst_unavailable: BZSt unreachable or in maintenancebzst_server_error: BZSt internal error on a known code