Troubleshooting

Token Authentication Error

Various errors related to authorization may occur. The following may help in solving any issues you might have:

  • The token must be provided in the Authorization header including the “Bearer” prefix
    • Authorization: Bearer msuw92n10snmdhywqaodwass=/
  • If token has expired, use the API Authentication to get a new one
  • If token is rejected (multiple scenarios) verify that token is being sent in the correct format

401 Authentication Errors

Copy 
{
"message": "token has expired",
"code": 401
}

 

Copy 
{
"message": "token rejected",
"code": 401
}

 

Copy 
{
"message": "no token supplied",
"code": 401
}

 

Copy 
{
"message": "jwt token not currently supported ",
"code": 401
}

 

Copy 
{
"message": "jwt token rejected (ERRNO 1)",
"code": 401
}

 

Copy 
{
"message": "jwt token rejected (ERRNO 2)",
"code": 401
}

 

Copy 
{
"message": "jwt token rejected (ERRNO 3)",
"code": 401
}

 

Unexpected Error

Oops! We’re not sure what went wrong. Please let us know and we will review.

503 Unexpected Error

Copy 
{
"message": "unexpected error",
"code": 503
}