Errors
What each error from Unify means and what to do about it, and the shape of a validation error.
Validation errors
422 means the document failed validation. errors lists every problem, so fix them all before you send the document again.
| Field | Type | Description |
|---|---|---|
code | string or null | The rule identifier when the check comes from a published rule, such as IBR-015 or a Saudi BR-KSA-* rule. |
getsPath | string or null | The field in GETS. |
payloadPath | string or null | The field in the payload you sent. |
message | string | What is wrong. |
severity | string or null | For example error. |
ruleSet | string or null | The rules the document was checked against, as country:documentType. |
validationStage is gets when a field or rule failed. When it is xml, producing the e-invoice failed and errors is empty: contact support with the documentId.
GETS-HEAD-010: the documentNumber was already sent. Change it and send the document again.
These errors come from submitting a document. The rules behind them differ by country, and each country lists its own: United Arab Emirates, Saudi Arabia, Malaysia, Oman, Belgium and Germany.
Other errors
| Status | Meaning |
|---|---|
400 | The request is malformed, names an unsupported country, or has no source. |
401 | The API key is missing, invalid, revoked or expired. |
403 | The key belongs to a different environment from environment, or cannot write. |
404 | The source is not in your workspace. |
412 | A production request was refused because the test cases your mapping requires have not passed yet. Run them in Testbeds, then send again. |
429 | Too many requests. Wait for the seconds in Retry-After, then retry. |
Try every one of these in the API playground.
Last updated