Pushwoosh API error responses and what causes them

Question: What error responses can the Pushwoosh API return, and what causes them?

Answer: Most errors come back with HTTP 200 and a JSON body containing status_code, status_message and response. Any status_code other than 200 (or, for some legacy methods, 210) means the request was not processed as intended.

• status_code 210, "Application not found" — the application parameter is set, but no application exists with that code.
• status_code 200, "Application suspended" — the application exists but has been suspended on your account.
• status_code 210, "Account not found" — the application or auth parameter resolves to an application, but there is no account behind it, or the auth token is missing or invalid.
• status_code 200, "Account has been suspended" — the account backing the application or API token is suspended.
• status_code 200, "You have exceeded the amount of active devices allowed on your current subscription plan" — the account has hit its device limit.
• status_code 210, "API token or application is not set" — the request is missing auth, application, or username/password.
• status_code 210, "User not found" — username/password were supplied but do not match any user.
• status_code 200, "Request postponed due to migration" — the account is currently being migrated between infrastructure; retry later.
• status_code 200, "OK" with a Warnings array — the request succeeded, but part of it was ignored. For example, sending both platforms and devices in one request causes platforms to be ignored.
• status_code 210, "Access denied or application not found" — the application code is invalid, or the token has no access to it.

Other HTTP-level errors you may encounter:

• 404 with an empty body or {"error": "record not found"} — the requested entity does not exist.
• 400 with an empty body — the API method does not exist, or a required parameter (for example hwid on /messageDeliveryEvent) is missing.
• 403 or 500 with an empty body — an internal error. If you see these consistently, contact support with the request details.