Skip to main content
sebastianc2022
New Participant
Nov 14, 2023 1:41 PM UTC
Solved

API POST Request Fails: APNX-1-4552-028

I'm attempting to use the Import endpoint of the Appian Deployment REST API v2. However, it continues to return the error listed below. I suspect that the error might be with the permissions with the service account associated with the API Key but cannot be certain. Is there any way to get more information on this error?

{"resource":"\/suite\/deployment-management\/v2\/deployments","title":"An Error Has Occurred","error":"APNX-1-4552-028","message":"Project is not accepting export requests via this endpoint. Contact your system administrator to configure this feature."}

sebastianc2022Answer
New Participant
Nov 15, 2023 3:48 PM UTC

I never found a complete solution to this, but it looks like using v1 (i.e. https://${{ secrets.APPIAN_DOMAIN }}/suite/deployment-management/v1/deployments) of the API resolves this error. It's unclear why v2 does not work.

The API v2 was not introduced until 23.3. The current version of my Appian Cloud is 23.2. A point that should be made very clear in the documentation.

View in thread

4 replies

peter.lewis
peter.lewis
Employee
Nov 14, 2023 2:48 PM UTC

Have you enabled external deployments in the Admin Console? That sounds like the likely culprit here: docs.appian.com/.../Appian_Administration_Console.html

sebastianc2022Author
New Participant
Nov 14, 2023 3:29 PM UTC

I turned it on, but it's still returning the same error. I'll add my API request below. Perhaps, there is an issue there.

curl --location --request \
POST 'https://${{ secrets.APPIAN_DOMAIN }}/suite/deployment-management/v2/deployments' \
--header 'Appian-API-Key: ${{ secrets.APPIAN_API_KEY }}' \
--header 'Action-Type: import' \
--form json='{
    "name": "Test Automation - Import Package",
    "packageFileName": "Test.zip" 
}' \
--form packageFileName=@'/packages/Test.zip'

sebastianc2022AuthorAnswer
New Participant
Nov 15, 2023 3:48 PM UTC

I never found a complete solution to this, but it looks like using v1 (i.e. https://${{ secrets.APPIAN_DOMAIN }}/suite/deployment-management/v1/deployments) of the API resolves this error. It's unclear why v2 does not work.

The API v2 was not introduced until 23.3. The current version of my Appian Cloud is 23.2. A point that should be made very clear in the documentation.

    Terms & ConditionsAccessibility statement