Reference
Error Codes
How to interpret error payloads today and what to expect as the public API hardens.
Current error model
Most endpoints return a JSON object with an error string describing the failure. There is not yet a separate stable machine-readable error code enum on every route.
Branch on HTTP status first, then show or log the error string for operators.
Example messages
Messages vary by route, but commonly cover invalid credentials, upload format rejection, plan limit blocks, missing jobs, inactive shares, and worker failures.
- Invalid email or password
- Unsupported or rejected upload format
- Upload exceeds plan limit
- Not signed in
- Share is inactive or revoked
- Job not found
Toward a public contract
Enterprise API packages may introduce explicit error codes alongside messages. When that ships, prefer codes for programmatic handling and keep messages for humans.
