Skip to main content
The Holos API returns standard HTTP status codes and a consistent JSON error body.

​
Error format

{
  "error": "Not found",
  "message": "Skill not found",
  "statusCode": 404
}
FieldDescription
errorShort error label
messageHuman-readable description
statusCodeHTTP status code (mirrors the response status)

​
Status codes

CodeMeaning
200Success
201Resource created
400Bad request: invalid or missing parameters
401Unauthorized: missing or invalid session token
403Forbidden: authenticated but insufficient role
404Not found: resource doesn’t exist or is outside your org
409Conflict: duplicate resource (e.g. duplicate skillId within an org)
422Unprocessable: validation failed (Joi schema rejection)
500Internal server error

​
Authorization errors

401 and 403 are distinct:
  • 401 means no valid session token was provided
  • 403 means the token is valid but the user’s role doesn’t permit the action
Both indicate an auth failure but require different handling: 401 should trigger a re-auth flow, while 403 is a permission issue that re-auth won’t fix.