Bad Request. This error typically occurs due to a problem with the format of request data, such as a non-parsing or invalid body of data, or an invalid set of query parameters or values.

The response's detail should clarify the problem. The response also features an optional errors array that potentially list more than one detected problem encountered at runtime.

This example represents a syntax problem in the schema. The provided value doesn't match the allowed enums. For 400 errors caused by schema mismatches, you can compare your request body against the schemaLink and schemaLocation. See Get a schema for a request for more details.

    "type": "https://problems.luna.akamaiapis.net/papi/v1/json-schema-invalid",
    "title": "Input does not match schema",
    "detail": "Your input has a syntax problem.  Please double check against the schema.",
    "instance": "/papi/v1/includes?contractId=1-12345&groupId=12345#abc12345abcc02a7",
    "status": 400,
    "schemaLink": "/papi/v1/schemas/request/CreateOrCloneIncludeRequestV0.json",
    "errors": [
            "location": "/includeType",
            "schemaLocation": "/properties/includeType",
            "detail": "instance value (\"COMMON_SETTINS\") not found in enum (possible values: [\"COMMON_SETTINGS\",\"MICROSERVICES\"])",
            "foundValue": "COMMON_SETTINS",
            "allowedValues": [

Possible types of 400 errors

PAPI may return different types of 400 error, depending on the cause of the problem:

  • Parameter problems. These errors indicate missing required path or query parameters, or invalid parameter values.
  • Property and include problems. These errors indicate problems with property or include data, such as invalid, too long or non-unique name, failed attempt to delete a property or include and others.
  • Property and include activation problems. These errors indicate problems with activation requests, such as missing or empty notifyEmails array, unresolved validation errors, unacknowledged validation warnings, activation pending cancellation, moving hostname from one account to another, failed attempt at cancelling the Fast Fallback activation and others.
  • Property version hostnames. These errors indicate problems with hostnames assigned to property versions, such as the cnameTo value referencing a non-existent edge hostname, missing or mismatched cnameTo and edgeHostnameId values and others.
  • Edge hostname problems. These errors indicate problems with an edge hostname, such as the specified edge hostname being unavailable, the edge hostname's specified domainPrefix or domainSuffix not being allowed, invalid or not allowed use case and others.
  • Hostname bucket problems. These errors indicate problems with a hostname bucket, such as failed attempt to save hostnames bucket or unsupported copyHostnames option.
  • Search problems. These errors indicate problems with a search request, such as missing required body field, missing request body, incorrect request body field and others.
  • Rule problems. These errors indicate problems with business rules that determine how content is delivered to your end users, such as unsupported rule format, non-parseable or invalid JSON file, unexpected data type of the rules file and others.