Pushwoosh API error responses and what causes them

Http code: 200 (OK).
Body:

{
  "status_code":    210,
  "status_message": "Application not found",
  "response":       null
}

Causes:

• 'application' parameter is set, but there's no application with this value

Http code: 200 (OK).
Body:

{
  "status_code":    200,
  "status_message": "Application suspended",
  "response":       null
}

Causes:

• • 'application' parameter is set, application with this value os found but it is 
  'isBackuped' == 1.

Http code: 200 (OK).
Body:

{
  "status_code":    210,
  "status_message": "Account not found",
  "response":       null
}

Causes:

• 'application' parameter is set, application with this value is found but there is no account
• 'auth' parameter is set, APIToken loaded, but there is no account
• 'auth' parameter is set, but there is no API token.
• 'auth' parameter is set, but it is invalid.

Http code: 200 (OK).
Body:

{
  "status_code":    200,
  "status_message": "Account has been suspended",
  "response":       null
}

Causes:

• 'application' parameter is set, Application and Account loaded, but the Account in 'isBackupAndRemove' == 1 or 2 status.
• application' parameter is set, Api Token and Account loaded, but the Account in 'isBackupAndRemove' == 1 or 2 status.

Http code: 200 (OK).
Body:

{
  "status_code":    200,
  "status_message": "You have exceeded the amount of active devices allowed on your current subscription plan",
  "response":       null
}

Causes:

• 'application' parameter is set, Application and Account loaded, but the Account in 'isSuspended' == true.
• application' parameter is set, API Token and Account loaded, but the Account in 'isSuspended' == true.

Http code: 200 (OK).
Body:

{
  "status_code":    210,
  "status_message": "API token or application is not set",
  "response":       null
}

Causes:

• Parameters 'auth' or 'application' or 'username' and 'password' not specified

Http code: 200 (OK).
Body:

{
  "status_code":    210,
  "status_message": "User not found",
  "response":       null
}

Causes:

• Parameters 'username' and 'password' is set, but there is not corresponding User to be found. Incorrect username or password. 

Http code: 200 (OK).
Body:

{
  "status_code":    200,
  "status_message": "Request postponed due to migration",
  "response":       null
}

Causes:

• The account is currently undergoing migration process.

Http code: 200 (OK).
Body:

{
  "status_code":    200,
  "status_message": "OK",
  "response":    {
  "Warnings": ["Platforms for devices list is not allowed"]
}
}

Causes:

• 'platforms' and 'devices' parameters are specified in one request. In this case, 'platforms' parameter is ignored.

Http code: 210 (OK).
Body:

{
  "status_code":    210,
  "status_message": "Access denied or application not found",
  "response":       null
}

Causes:

• Invalid application code.

Http code: 401 (Unauthorized).
Body:

{
  "error":         "authorization error",
  "message":       "Please provide a valid authentication token parameter or HTTP Authorization header.",
  "reference_url": "https://zeropush.com/documentation/api_reference"
}

Causes:

• HTTP-authorization parameters are not set or set incorrectly.

Http code: 404 (Not Found) ('Internal error' in some obscure cases.
Body:

{
  "error": "record not found",
}

or

<empty body>

Causes:

• Various type of entities cannot be found.

Http code: 400 (Bad Request) ('No API method' in some cases).
Body:

<empty body>

Causes:

• No such method
• 'hwid' parameter is not set in (/json/1.3/messageDeliveryEvent).
• Other reasons.

Http code: 403 (Forbidden).
Body:

<empty body>

Causes:

• Various internal reasons.

Http code: 500 (Internal server error).
Body:

<empty body>

Causes:

• Various internal reasons.