This section shows you how to handle various kinds of error responses the Property Manager API generates. In addition to standard HTTP error responses, it discusses how to deal with errors from variables as they're interpreted on the edge once you activate a property. This section also lists the range of HTTP response codes, provides details for many API-specific error messages along with their likely causes, and reports any known issues remaining in the current API release.

For information how to resolve PAPI-specific errors and warnings reported in rule trees before you activate a property, see Rule tree errors and warnings.

Problem Details object

API operations routinely respond with failure codes to a wide range of problems with the integrity of the data you're trying to modify, everything from malformed JSON, to missing fields, to mismatching etags digests. If an error occurs, this API responds with Problem Details JSON objects that follow the RFC 7807 specification and provide you with the information to debug the problem.

This example shows an access error due to insufficient permissions configured in Akamai Control Center, where the type value is a non-navigable URI, and the instance may be useful if you need to communicate about the problem with your ​Akamai​ support representative:

{
    "type": "https://problems.luna.akamaiapis.net/papi/v1/http/forbidden",
    "title": "Forbidden",
    "detail": "The authorization token you provided does not allow access to this resource.",
    "instance": "/papi/v1/properties?contractId=ctr_123452&groupId=grp_12345",
    "status": 403
}

For details on information contained in the error responses, refer to Error response syntax.

JSON request schema errors

400 errors about malformed data typically reference schema objects that describe whichever resource you're trying to interact with. PAPI provides a separate Request schema interface for these objects that reference specific schema files.

For example, this schema describes the expected data structure when creating a new edge hostname:

GET /papi/v1/schemas/request/EdgeHostnamesPostRequestV0.json