Errors & troubleshooting¶
Arena’s Swagger/OpenAPI is the source of truth for endpoints and schemas.
This page supplements it with practical guidance for investigating failures.
✅ Success Codes¶
| Code | Meaning |
|---|---|
| 200 | OK - default success message |
| 201 | Created - success and new entity created |
| 204 | No content - success but no content in response (e.g. DELETE Item) |
❌ Error Codes¶
| Code | Meaning |
|---|---|
| 400 | Bad request - syntax error in the request |
| 403 | Forbidden - user doesn’t have proper privileges |
| 401 | Unauthorized - valid access token required but not specified |
| 404 | Resource not found - endpoint not supported |
| 409 | Item number already exists - duplicate item numbers not allowed |
| 415 | Unsupported media type - no or wrong content-type specified |
| 429 | Too many requests - maximum API request limit reached for 24-hour period |
What to include when opening a ticket¶
- Endpoint (e.g.,
POST /items/{guid}/bom), request JSON, response code/body, workspace ID, user email. 1
See also: error handling and success codes in the GitHub docs for additional examples. 3