Error Handling

The subsequent sections provide a description of the HTTP errors and the format of the error responses.

Unauthenticated Requests

{
  "statusCode": 401,
  "message": "Unauthorized"
}

Forbidden Requests

{
  "statusCode": 403,
  "message": "Message of the error"
}

Not Found Requests

{
  "statusCode": 404,
  "message": "Not Found"
}

Bad Requests

{
  "statusCode": 400,
  "message": "Bad Request Exception",
  "extra": {
    "response": {
      "message": [
        "Dates must be within the last 120 days."
      ],
      "error": "Bad Request",
      "statusCode": 400
    },
    "status": 400,
    "options": {},
    "message": "Bad Request Exception",
    "name": "BadRequestException"
  }
}

{
  "statusCode": 400,
  "message": "Invalid type",
  "extra": {
    "response": {
      "message": "Invalid type",
      "error": "Bad Request",
      "statusCode": 400
    },
    "status": 400,
    "options": {},
    "message": "Invalid type",
    "name": "BadRequestException"
  }
}

Unprocessable Entity

{
  "statusCode": 422,
  "message": "Message of the error"
}

Too Many Requests

{
  "statusCode": 429,
  "message": "ThrottlerException: Too Many Requests"
}

Internal Server Error

{
  "statusCode": 500,
  "message": "Internal Server Error Message"
}

if you consistently get internal server error, please contact us at aped-tms@9and9.com.

Last modified: 04 December 2024