There are two versions of the deployment REST API. If your environment is on version 23.2 or earlier, use version 1. If your environment is on version 23.3, use version 2 to enable programmatic export of applications and packages.
Appian's deployment REST API suite provides a secure way to expose Appian deployment services and data via external systems.
These deployment APIs allow you to:
With Appian's native APIs, you can completely automate your CI/CD pipeline, including your Appian exports, inspections, and imports. They also allow you to configure a post-deployment process to run after external deployments. There are five endpoints available for deployments:
In addition to these capabilities, you can also use the Application Package Details to retrieve package identifier information to trigger your deployments.
This page gives an overview of Appian's deployment REST API suite. You can enable these deployment APIs for use on your environment in the Admin Console infrastructure page.
Note: The API follows REST standards. See this resource for more information about RESTful APIs.
All deployment API endpoints are called with a URL beginning with https://<domain>/suite/deployment-management/v2, where <domain> is replaced with your Appian site domain and <v#> specifies the version of the endpoint you are using.
Every API endpoint must be called using the HTTP request method (POST or GET) specified in the documentation. A POST request is used to send data to (in the case of import) or retrieve data from (in the case of export) Appian. A GET request is used to request data from Appian, such as retrieving the status of an existing deployment or retrieve the corresponding deployment log.
Tip: GET requests are always available regardless of Admin Console settings for controlling incoming and outgoing deployments.
All endpoint requests are authenticated with an API key, which is linked to a service account. This is the same mechanism that Appian uses to secure Web API objects. The service account and API key can be created in the Admin Console, and then configured to secure external deployments.
Once configured, there are multiple ways to use the API key to authenticate your request. For example, you can add it to the HTTP header with the key name Appian-API-Key:
curl https://<domain>/suite/deployment-management/v2/deployments -H "Appian-API-Key: <API key>"
For any GET requests, users can use the provided URL in their browser to retrieve results. As long as that user has the correct access to the application to see deployment details they will be able to see the results.
The same sets of endpoints are used for incoming and outgoing deployments. For POST requests where you need to differentiate between imports and exports, you can specify the Action-Type in the header alongside your Appian-API-Key.
curl https://<domain>/suite/deployment-management/v2/deployments -H "Appian-API-Key: <API key>" -H "Action-Type: <import/export>"
Appian recommends inspecting all packages before deployment. Additionally, the export endpoint should be used with an change management system to ensure only work that is ready for deployment is being exported.
The high-level workflow and endpoints for each step are:
export and extract the desired deployment package. When deploying a package, any database scripts, plug-ins, or import customization file specified in the package will be available as resources of the deployment once it completes./deployments/<uuid> endpoint. Once it completes, you will be able to download the corresponding resources created from your deployment./deployments/<uuid>/log endpoint./inspections endpoint. The endpoint response provides the UUID of the inspection, which you can use in the next step./inspections/<uuid> endpoint. The inspection may take longer depending on the size of your package. Appian recommends hitting this endpoint on a regular interval until the inspection is complete and results are available, which is indicated by the status response./deployments endpoint. This is the same endpoint used in step 1. You can set the Action-Type to import, otherwise the value is set to import by default. The endpoint’s response provides the UUID of the deployment, which you can use in the next step./deployments/<uuid> endpoint. As in step 2, the deployment time will vary with the size of your package. Appian recommends hitting this endpoint on a regular interval until the deployment is completed and results are available, which is indicated by the status response./deployments/<uuid>/log endpoint.Appian's deployment REST API suite provides a safe way to expose Appian deployment services and data to external systems.
This allows you to:
There are five endpoints that allow you to inspect and deploy Admin Console settings, applications, packages, import customization files, plug-ins, and database scripts. They also allow you to configure a post-deployment process to run after external deployments.
The endpoints are:
This page gives an overview of Appian's deployment REST API suite. You can enable these deployment APIs for use on your environment in the Admin Console infrastructure page.
Note: The API follows REST standards. See this resource for more information about RESTful APIs.
All deployment API endpoints are called with a URL beginning with https://<domain>/suite/deployment-management/v1, where <domain> is replaced with your Appian site domain.
Every API endpoint must be called using the HTTP request method (POST or GET) specified in the documentation. A POST request is used to send data to Appian in order to create or update information, such as creating a new deployment. A GET request is used to request data from Appian, such as retrieving the status of an existing deployment.
All endpoint requests are authenticated with an API key, which is linked to a service account. This is the same mechanism that Appian uses to secure Web API objects. The service account and API key can be created in the Admin Console, and then configured to secure external deployments.
Once configured, there are multiple ways to use the API key to authenticate your request. For example, you can add it to the HTTP header with the key name Appian-API-Key:
curl https://<domain>/suite/deployment-management/v1/deployments -H "Appian-API-Key: <API key>"
Appian recommends that any package should first be inspected and then deployed.
The high-level workflow and endpoints for each step are:
/inspections endpoint. The endpoint response provides the UUID of the inspection, which you can use in the next step./inspections/<uuid> endpoint. The inspection may take longer depending on the size of your package. We recommend hitting this endpoint on a regular interval until the inspection is complete and results are available, which is indicated by the status response./deployments endpoint. The endpoint’s response provides the UUID of the deployment, which you can use in the next step./deployments/<uuid> endpoint. Similar to step 2, the deployment time will vary with the size of your package. We recommend hitting this endpoint on a regular interval until the deployment is completed and results are available, which is indicated by the status response./deployments/<uuid>/log endpoint.