HTTP Status Codes

Describes the Status Codes returned by Cloud API

The following table explains the different HTTP Status Codes with their corresponding response.

Status Codes

Response

Description

200

{"results":["<string>","<string>"],
 "success": true, "encoding":[hex|utf8]}

Success protected data is in results, and success attribute is true

400

{
    "error_msg": "<string>",
    "success": false
}

There was an issue in the request, success is false, check error_msg attribute. For more information check AWS Lambda’s CloudWatch logs.

For example, the following error appears.

Authorization header was not found.
  1. Required attribute is missing /user, when env authorization is None or empty.
  2. User is missing, check JWT payload for user attribute
  3. Malformed authorization header
  4. Basic Not supported in header: authorization

403

{
    "error_msg": "token expired",
    "success": false
}

{
    "error_msg": "invalid signature",
    "success": false
}
{
    "error_msg": " unknown algorithm error",
    "success": false
}
  1. JWT is invalid because secret is wrong or expired.
  2. Get A new JWT or check the base64 secret in AWS Lambda environment variable.
  3. Secret doesn’t match the algorithm type in the JWT header. Secret is symmetric but Algorithm is asymmetric.

500

{
    "error_msg": "Invalid json array in jwt_user_claim",
    "success": false
}

{    "error_msg": "jwt secret is missing ",
    "success": false
}
  1. Configuration error in AWS Lambda.

Authorization is to JWT and jwt _user_claim is not a valid json array. Example valid input: [“username”, “firstname”].

  1. JWT is set to verify and jwt_secret_base64 is missing.

Last modified : January 21, 2026