Global Traffic Management Reporting API Debugging

This section tells you what you need to know about the GTM Reporting API’s error response format, and details the range of HTTP status codes the API produces.

Error Responses

EdgeGrid responds with HTTP problem error objects that provide details useful for debugging. 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/data-dns/v1/traffic/xxx.xxxxxxxxx.xxx?20150411&00:00&20150414&23:59&EST&false",
  "method" : "GET",
  "serverIp" : "nnn.nnn.nnn.nnn",
  "clientIp" : "nnn.nnn.nnn.nnn",
  "requestId" : "372819f9",
  "requestTime" : "2015-04-16T14:56:52Z"
}

HTTP Status Codes

The API produces the following set of HTTP status codes for both success and failure scenarios:

Code Description
200 Request OK
400 Bad Request
401 Unauthorized Request
403 Forbidden
404 Resource not found
405 Method not allowed

Last modified: 6/2/2017