Diagnostic Tools API v1 Debugging

This section shows you how to handle various kinds of error the API generates, and lists the range of HTTP codes the API produces for both success and error scenarios.

JSON Problems

The OPEN API platform returns HTTP Problem error objects. For example:

{
    "type": "https://problems.luna.akamaiapis.net/-/pep-authn/request-error",
    "title": "Bad request",
    "status": 400,
    "detail": "Authorization header missing",
    "instance": "https://akab-xxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxx.luna.akamaiapis.net/diagnostic-tools/v1/locations",
    "method": "GET",
    "serverIp": "NNN.NNN.NNN.NNN",
    "clientIp": "NNN.NNN.NNN.NNN",
    "requestId": "xxxxxxxx",
    "requestTime": "2015-04-16T14:56:52Z"
}

In most cases, the type and title provide enough information to understand the nature of the error.

Please be sure to reference the problem type when communicating with Akamai representatives or the Akamai Developer Community.

HTTP Status Codes

Code Description
200 Request OK
201 Resource created
401 Unauthorized request
402 Failed request
403 Forbidden
404 Resource not found
405 Method not allowed
415 Unsupported media type
422 Unprocessable entity
429 Too many requests
5xx Server error

Last modified: 4/14/2017