POST /api/deploymentzones

Adds a deployment zone on the platform.

Authorization Roles/Permissions: Must be logged in. Must have Add permission for the resource. For example, a Business Admin.

This topic includes the following sections:

HTTP Method


Back to top



Back to top

Sample Request

The example below shows a request to add a deployment zone.

Request URL


Sample request headers

POST /api/deploymentzones HTTP/1.1
Accept: application/json, text/javascript, */*; q=0.01
Content-Type: application/json

Sample request body


Back to top

Request Headers

For general information on request header values, refer to HTTP Request Headers.

Header Description

application/json, application/xml

application/vnd.soa.v81+json, application/vnd.soa.v81+xml


Any one of the following media types is valid for the request Content-Type:

application/json or application/xml

application/vnd.soa.v81+json or application/vnd.soa.v81+xml

X-Csrf-Token_{fedmemberID} The CSRF prevention header; may or may not be required, depending on platform settings. See CSRF Prevention on the Platform. By default, the CSRF header is not required for GET operations and is required for all others, with a few exceptions relating to user login.

Back to top

Request Parameters

Parameter Parm Type Data Type Required Description
deploymentZoneInfo Body DeploymentZoneInfo Required

Contains information about a specific deployment zone on the platform.

Minimum properties in the request: RandomHostNameBehavior, Name, Description, ContainerKey, AddressOverrideBehavior, VirtualHostSupported.

Back to top


If successful, this operation returns HTTP status code 200, with information about the new deployment zone, including its implementation/environment associations.

Back to top

Sample Response

The sample response below shows successful completion of this operation.

Sample response headers: application/json

HTTP/1.1 200 OK
Date: Thu, 15 Sep 2016 21:01:11 GMT
Content-Type: application/json

Sample response body: application/json

  "DZoneEnvImplAssociations" : {
    "DZoneEnvImplAssociation" : [ {
      "Implementation" : "Live",
      "Environment" : "Production"
    }, {
      "Implementation" : "Sandbox",
      "Environment" : "Production"
    } ]
  "DeploymentZoneID" : "2fbb5c83-6a91-455e-9d36-17a013812302.acmepaymentscorp",
  "Name" : "EAP_ND",
  "Description" : "EAP_ND",
  "ContainerKey" : "39lvglP7TiywePHw_vD3Kg",
  "ContainerName" : "eapndTrunk",
  "AddressOverrideBehavior" : "com.akana.dontallow",
  "RandomHostNameBehavior" : "com.akana.dontallow",
  "VirtualHostSupported" : false,
  "DeploymentZoneAccessPoint" : [ {
    "Protocol" : "http",
    "Name" : "default-http0",
    "Address" : ""
  } ]

Back to top

Response Headers

For general information on response header values, refer to HTTP Response Headers.

Header Description

application/json, application/xml

application/vnd.soa.v81+json, application/vnd.soa.v81+xml

Back to top

Response Body

Name Type Description
DeploymentZoneInfo DeploymentZoneInfo Contains information about a specific deployment zone on the platform.

Back to top

Error Codes/Messages

If the call is unsuccessful an error code/message is returned. One or more examples of possible errors for this operation are shown below.

Item Value
401 Unauthorized. For example, you would get this response if you didn't include the custom X-Csrf-Token_{fedmemberID} header in the request, when it was required by the platform settings; or if you included an invalid or expired value for this header. You would also get this response for any operation that requires login (almost all) if the login cookie was missing.
500 An error occurred processing the call.

More information about Akana API Platform API error messages.

Back to top

Related Topics