The Traffic Management API Debugging

This section provides the full set of error messages and status codes the Traffic Management API may generate.

Code Message Description
400 Invalid Entity Returned when the request entity failed validation of one form or another. The response entity’s detail field contains a message describing what failed validation, and in most cases gives a hint on how to correct the problematic value.
400 Malformed Request Entity Returned when the server could not parse the JSON entity sent by the client. The response entity’s detail field contains the message returned from the JSON parsing library, but it may not contain enough information on what is wrong. The best course of action is for the client to validate the JSON payload using the appropriate JSON schema to identify the problem.
400 Datacenter in use Returned when a client requests to DELETE a data center, but that data center is in use by one or more Properties, and/or one or more Resources. Reassign such Properties or Resources to use alternate datacenters, at which point a subsequent request to DELETE is allowed and processed.
400 ACG ID Invalid This error is returned at domain creation time. If the Domain representation contains an invalid ACG ID, or an ID which the client does not have access to. Best to leave this field blank, as the server assigns an appropriate ID automatically.
400 Type mismatch This error is returned if a query string can not be parsed into the expected type (e.g. if the parameter expects an integer, and contains alphabetic characters). The response entity’s invalidValue field contains the value that could not be parsed.
400 Datacenter ID mismatch Returned when when a client PUTs a JSON representation to a data center resource of a datacenterId (e.g. /datacenters/3131), but the JSON’s datacenterId field does not match that resource id (e.g., {"datacenterId": 3231, ...}).
400 Domain name mismatch Returned when when a client PUTs a JSON representation to a Domain resource of a name (e.g. /domains/mydomain.akadns.net), but the JSON’s name field does not match that resource name (e.g., {"name": "myotherdomain.akadns.net", ...}).
400 Property name mismatch Returned when when a client PUTs a JSON representation to a Property resource of a name (e.g. /properties/foo), but the JSON’s name field does not match that resource name (e.g., {"name": "baz", ...}).
400 Map name mismatch Returned when when a client PUTs a JSON representation to a Geographic or CIDR Map resource of a name (e.g. /geographic-maps/mymap), but the JSON’s name field does not match that resource name (e.g., {"name": "myothermap", ...}).
400 Resource name mismatch Returned when when a client PUTs a JSON representation to a Resource resource of a name (e.g. /resources/cpu), but the JSON’s name field does not match that resource name (e.g., {"name": "disk", ...}).
400 CIDR Map Default datacenter ID must be assigned This error occurs when creating a CIDR Map. Ensure that the request’s JSON representation has left the defaultDatacenter object’s datacenterId field blank, as it is assigned by the server.
400 Datacenter ID must be assigned Returned when when a client POSTs a JSON representation to create a new data center, but the JSON’s datacenterId has not been left blank. This field must be blank, as a datacenterId must be assigned by the server.
400 Domain Type Required This error only occurs when creating a domain. The JSON representation’s type field must be populated with one of the four valid domain types: failover-only, static, weighted, or basic.
400 Performance Plus Domains can not be created This error only occurs when creating a domain. If the JSON specifies a type of full, this error is returned as domains of this type can not be created with this API. Please contact Akamai customer support for assistance in creating such domains.
400 Domain Type not allowed This error only occurs when creating a domain, if the JSON specifies a domain type which is not permitted due to contractual restrictions. For instance, if Weighted Load Balancing has been purchased, only Failover and Weighted domains are allowed.
403 Forbidden Returned when the client’s credentials were verified, but did not have authorization to access the requested resource.
404 Not Found Returned when a named resource, be it a domain, data center, property, resource, geographic or CIDR map, or status, does not exist.
405 Method Not Supported Returned when the server does not support a specific request method. The response entity’s detail field contains a list of supported methods for the Resource, for reference.
406 Not Acceptable Returned when the server can not represent a resource using the requested media type. The response entity’s minimumMediaTypeRequired field lists the minimum version media type required to successfully render the resource. See API Versioning for more information.
409 Datacenter Conflict Returned when a request to create a data center with a specific datacenterId, but a data center with that ID already exists.
415 Unsupported Media Type (entity content type) Returned when when a client POSTs, PUTs, or PATCHes content of a type that is not supported. For version 1, application/json, application/vnd.config-gtm.v1.0+json (both are synonymous with each other) and for version 2, application/vnd.config-gtm.v1.1+json, are supported.
415 Unsupported Media Type (acceptable entity type) Returned when the server cannot generate a response that is acceptable by the client. For version 1, application/json, application/vnd.config-gtm.v1.0+json (both are synonymous with each other) and for version 2, application/vnd.config-gtm.v1.1+json, are supported.
500 Unable to assign new domain This error only ever occurs when creating a new domain, if the server is unable to find a suitable ACG ID for the new domain. This typically occurs when clients do not have Traffic Management enabled on their contract, or lack access to contracts that do have access. Please contact Akamai customer support for assistance if you believe this is not the case.
500 Internal Server Error Something has gone wrong on the server side. The server does not have a modified state if this happens. Safegaurds are in place to make sure everything is as it was when the request began. A client may retry the request, but it is likely that failure will remain a consistent outcome, in which case the user is encouraged to contact Akamai customer support for assistance.

Last modified: 12/12/2016