Errors and Troubleshooting

Common Errors

These are common error types you might encounter when using the Bear API. We follow gRPC status codes, and where applicable, include structured error details using google.rpc.Status and related types (e.g., BadRequest, ErrorInfo).

Robot software incompatible

The robot’s software version does not meet the compatibility requirements of the API.
Code: FAILED_PRECONDITION
Resolution: Check the robot software version compatibility checklist. Starting with API v1, calls return appropriate errors when a version mismatch is detected.

Authenticated error

The request is missing valid authentication credentials (e.g., invalid token, expired session).
Code: UNAUTHENTICATED
Resolution: Confirm that the API key or JWT token is correct and has not expired. Refer to the authentication guide for how to obtain and refresh a JWT token using your API key.

Permission Denied

The request was authenticated, but the client does not have permission to access the requested resource.
Code: PERMISSION_DENIED
Resolution: Verify that the API key's user has the necessary permissions for the target robot or location. Tip: Double-check the spelling of all robot_id and location_id values.

Request fails validation

The request payload is well-formed, but contains invalid or missing values.
Code: INVALID_ARGUMENT
Resolution: Review the request against the API schema. The error message will typically include FieldViolation entries to help you pinpoint the issue.