The CalderaConnect REST API uses standard HTTP status codes and, on many routes, a problem payload compatible with RFC 7807.
Problem payload fields
A problem response can include:
- type
- title
- status
- detail
- instance
Common status codes
- 400 : bad request
- 403 : forbidden
- 404 : resource not found
- 405 : method not allowed
- 413 : payload too large
- 415 : unsupported media type
- 500 : internal or unknown server error
- 502 : remote server returned an error
- 503 : service unavailable or unsupported by the target service
Typical situations
- image import failures often return 400, 405, 413, or 415
- device state changes often return 400, 403, 404, or 500
- job lifecycle routes often return 404 or 502
- machine information can return 503 if the target service cannot provide it
Examples
401 CalderaCare is not in the license
The Caldera REST API is exclusive to users with a CalderaCare subscription. If you try to use the tool without the corresponding license, an error 401 will appear.
Contact our sales team for more information.