Alerts API Debugging

When you encounter an error, the Alerts API responds with HTTP problem objects that provide details useful for debugging, as in the example below. In some cases, 502 or 503 routing errors may respond with HTML generated from the application server.

{
    "code": "internal.server.error",
    "title": "Internal Server Error",
    "helpUrl": null,
    "incidentId": null,
    "resolution": null,
    "stackTrace": null,
    "details": [
        {
            "code": "alerting.unhandled.exception",
            "data": null,
            "field": null,
            "message": "java.lang.IllegalStateException: [You do not have access to id(s) [73887] of type [adaptivecpcode]]"
        }
    ]
}

HTTP Status Codes

The Alerts API responds with the following range of status codes:

Code Description
200 Request OK.
201 Successfully created.
204 Successfully updated or deleted.
400 Badly formatted JSON. Compare with the schema.
401 Platform error, likely an expired or missing token.
403 Application permission error.
404 Content unavailable or inaccessible.
500 Internal error. See JSON error response for details.
502 Platform timeout error.
503 Unspecified platform error.

Last modified: 12/6/2016