Errors
How to think about failure, validation, and permission errors in Infrenta integrations without a public error-code table.
Until a public API contract is published, there is no stable public error-code table to document.
Inside the product, failures generally fall into:
- validation — the payload or document cannot be compiled or saved
- permission — the user or integration lacks the module or record scope
- conflict — a draft row version or revision does not match
- not found — the project or record is missing or is in another company
Integrations should treat “not found” and “not allowed” as equivalent from a data-leak perspective: do not probe other companies.
When a public contract exists, this page will list the stable error shapes for that contract only.