error.code before reading data.
Codes
| Code | HTTP | What to do |
|---|---|---|
UNAUTHORIZED | 401 | Missing or invalid auth. Check the Authorization header |
FORBIDDEN | 403 | Authenticated but not allowed for this resource |
VALIDATION_ERROR | 400 | Body failed schema validation. details.path points at the field |
INVALID_JOB_TYPE | 400 | Job type not registered or not on your plan |
INSUFFICIENT_CREDITS | 402 | Top up at app.rendobar.com/billing |
PLAN_LIMIT | 403 | Plan limit hit (concurrency, file size). See Limits |
RATE_LIMITED | 429 | Back off per Retry-After header |
NOT_FOUND | 404 | Resource doesn’t exist or isn’t visible to your org |
CONFLICT | 409 | Request conflicts with current state (e.g. cancelling a complete job) |
RUNNER_ERROR | 502 | Processing failed on the runner. Check error.message for details |
RUNNER_TIMEOUT | 504 | The job did not finish in time. No credits charged |
ORG_SUSPENDED | 403 | Contact hello@rendobar.com |
INTERNAL_ERROR | 500 | Server bug. Persist? Contact support with the request ID |
Handle the common ones
The three you’ll hit most:INSUFFICIENT_CREDITS, RATE_LIMITED, VALIDATION_ERROR.
See also
Related
- Plan limits: caps behind
PLAN_LIMITandRATE_LIMITED - Job lifecycle: where
RUNNER_ERRORandRUNNER_TIMEOUTsurface - Credits and billing:
INSUFFICIENT_CREDITSand the prepaid model - FAQ: common questions about failed jobs and refunds
- Pricing: plan that lifts your concurrency and rate caps