Errors & Statuses
Truztcube verification statuses and error codes, with cause and recovery.
Truztcube uses a consistent error and status model across every verification type.
Verification statuses
A verification resolves to one of a small set of statuses — for example a successful match, a "no record found" (distinct from a system failure), or a failure. Your integration should branch on the status, not just the HTTP code.
HTTP status codes
| Code | Meaning |
|---|---|
200 | Request processed — check the body status for the verification outcome. |
400 | Invalid request — a required field is missing or malformed. Not billed. |
401 | Missing or invalid API key. |
402 / 403 | Insufficient wallet balance or not entitled to this service/access level. |
429 | Rate limited — retry with backoff. |
5xx | A Truztcube or upstream error — safe to retry. Not billed. |
Billing on errors
Validation rejections, entitlement errors, and upstream failures are never billed. Only a successful, completed verification debits your wallet.
Idempotency
Supply an Idempotency-Key header so a retried request never runs twice or double-charges.