GET /api/deploymentzones

Returns a list of valid deployment zones on the platform, in the form of an RSS channel.

Note: Be sure to include a valid Accept header with this operation. If you don't include the Accept header, the operation might fail in versions later than 8.0, even if it worked in earlier versions.

For more information on deployment zones, refer to Deployment Zones on the Platform.

Note: At this time, there is no interface to manage deployment zones in the platform. Deployment zone configuration is optional. Deployment zones are loaded in the DEPLOY_ZONES and DEPLOY_ZONE_CONTAINER tables using a database script. If no deployment zones are configured, the platform API constructs transient deployment zones based on the deployment configuration of the agents available for the platform to host API proxy endpoints. To manage the deployment zones in the platform, contact tech support.

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

This topic includes the following sections:

HTTP Method


Back to top



Back to top

Sample Request

The example below requests a list of deployment zones.

Sample request URL


Sample request headers

GET /api/deploymentzones HTTP/1.1
Accept: application/json

Sample request body

Not applicable.

Back to top

Request Headers

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

Header Description

application/json or text/xml

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

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

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

Content-Type Any format (*/*)
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
ApiID Query string Optional The API ID. If this parameter is included, only deployment zones available to the specified API are returned.

Back to top


If successful, this operation returns HTTP status code 200, with a list of available deployment zones. The information is sent as an RSS channel in JSON or XML format.

Back to top

Sample Response

The sample response below shows the list of deployment zones returned as an RSS channel.

Sample response headers

HTTP/1.1 200 OK
Date: Mon, 30 Jul 2018 20:10:06 GMT
Content-Type: application/json

Sample response body: application/json

  "channel": {
    "title": "Deployment Zones",
    "item": [
        "title": "ed33-ae99-463a-b663-75710bdb67fb",
        "link": "",
        "category": [
            "value": "Production",
            "domain": ""
            "value": "Sandbox",
            "domain": ""
        "guid": {
          "value": "ed33-ae99-463a-b663-75710bdb67fbdefault-http0"
        "EntityReferences": {
          "EntityReference": [
              "Title": "ed33-ae99-463a-b663-75710bdb67fb",
              "Guid": "ed33-ae99-463a-b663-75710bdb67fb.acmepaymentscorp",
              "Category": [
                  "value": "dzone",
                  "domain": ""
  "version": "1.0"

Sample response body: text/xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss xmlns:ns2="" xmlns:ns3="" xmlns:ns4="" xmlns:ns5="" xmlns:ns6="" xmlns:ns7="" xmlns:ns8="" xmlns:ns9="" xmlns:ns10="" xmlns:ns11="" xmlns:ns12="" xmlns:ns13="" xmlns:ns14="" xmlns:ns15="" xmlns:ns16="" xmlns:ns17="" xmlns:ns18="" xmlns:ns19="" xmlns:ns20="" xmlns:ns21="" xmlns:ns22="" xmlns:ns23="" xmlns:ns24="" version="1.0">
    <title>Deployment Zones</title>
      <category domain="">Production</category>
      <category domain="">Sandbox</category>
          <ns4:Category domain="">dzone</ns4:Category>

Back to top

Response Headers

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

Header Description

application/json or text/xml

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

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

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

Back to top

Response Body

The response body is an RSS channel titled Deployment Zones, which includes an array of one or more deployment zone items. Each item includes the fields listed below.

Name Description
Title Title of the deployment zone.
Link URL for the deployment zone.
Description Description of the deployment zone.
Category One or more categories, each with a value of Sandbox or Production, and each with a Domain property.
GUID GUID for the deployment zone.
Entity references

One or more entity references. Each includes:

  • Title
  • GUID: the unique ID for the item.
  • Category

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