The exposed Appian RPA API is a REST API. This format makes it far easier to invoke the functionality available in the API from other systems, even by using commands from different operating systems.
A typical URL to call the API methods matches the following format: protocol://rpa-server/rest/specific-part-for-the-method
The URL shown in the API methods section of this document corresponds to
Authentication in Appian RPA requires an API key via a service account from Appian.
If the service account has an administrator role in Appian, it will have an administrator role in Appian RPA. If the service account has a designer role in Appian, it will have a developer role in Appian RPA.
If the authentication has been successful, the REST API will return a token that must be used in the following invocations to the API. This token may be considered as a session identifier.
Every API method must be invoked using the HTTP verb described on their corresponding specifications.
The read methods will commonly use the GET verb, the update ones will use PUT or POST, those removing information DELETE, etc.
All the parameters must be included as the HTTP GET requests do, i.e., using query parameters, with the following exceptions:
The authentication method uses the verb HTTP POST with the request body of type x-www-form-urlencoded.
The method for the execution of robots with parameters uses the verb HTTP POST with the request body of type raw (application/json).
This information is included in every method specification.
The responses to the requests will always be obtained in JSON format.
Except for the authentication method, the responses will always include the following attributes:
It represents the result of the call. Its possible values are:
It represents the functional result of the call. Its value varies depending on the request made. The details can be found in every method specification described in this document.
On This Page