Enterprise Threat Protector Configuration API Debugging

This section provides details on the data object that reflects the API’s common response to error cases, and lists the API’s range of response status codes for both error and success cases.

Error Responses

EdgeGrid responds with HTTP Problem error objects that provide details useful for debugging. For example:

{
    "type": "https://problems.omni.akamaiapis.net/http/forbidden",
    "title": "Forbidden",
    "detail": "Insufficient permissions. Code-01",
    "status": 403,
    "instance": "3e3f11da-e205-409a-be77-24e459f29fa8"
}

HTTP Status Codes

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

Code Description
200 The operation was successful.
403 Access is forbidden.
404 Resource not found.
406 Not acceptable.
409 Conflict with current state of resource.
412 An Etag or If-Match header does not match, indicating the content has been modified. See Object Versioning for more information.

Last modified: 8/18/2017