Error Reference
All API errors return a standard JSON format:
{ "status": "error", "error": { "code": "RS-VAL-001", "message": "Missing required fields", "details": "robot_name is required", "help_url": "[https://docs.ridescan.ai/errors/RS-VAL-001](https://docs.ridescan.ai/errors/RS-VAL-001)" }}Common Error Codes
Section titled “Common Error Codes”| Code | HTTP Status | Message | Likely Cause |
|---|---|---|---|
| RS-AUTH-001 | 401 | Authentication failed | Missing or invalid API Key/Token. |
| RS-AUTH-002 | 403 | Role not authorized | User does not have permission. |
| RS-VAL-001 | 400 | Missing required fields | Request body is missing mandatory params or criteria. |
| RS-VAL-003 | 400 | Invalid input value | Sending an invalid enum (e.g., robot type “Terminator”). |
| RS-VAL-004 | 400 | Invalid parameter / Not Found | Often occurs if a Mission ID does not belong to the provided Robot ID. |
| RS-ROBOT-001 | 409 | Robot name exists | You tried to create a robot with a duplicate name in your Org. |
| RS-ROBOT-002 | 404 | Robot not found | Robot UUID is incorrect or you do not have access to it. |
| RS-MSN-001 | 409 | Mission name conflict | A mission with this name already exists on this robot. |
| RS-SYS-001 | 500 | Internal System Error | Database failure or unhandled exception. Contact Support. |
File Upload Errors
Section titled “File Upload Errors”| Message | Likely Cause |
|---|---|
| Unsupported file type | Uploading a file that is not .bag, .zip, or .csv. |
| No robot or mission existing | The provided UUIDs do not match any record in your organization. |
| No file provided | The files or file form field was empty. |