Comparing Automation 360 and Enterprise 11 APIs
Compare Automation 360 and Enterprise 11 APIs to understand the contract changes when you migrate from Enterprise 11 to Automation 360.
API details | Enterprise 11 | Automation 360 |
---|---|---|
Authentication API: Use this API to obtain the authentication token. The token is then used for all subsequent API calls. | ||
Method | POST | POST |
Endpoint | v1/authentication |
v1/authentication |
Request body changes | Not applicable | No change |
Response body changes | Not applicable |
|
Auto login credentials API: Use this API to set the Windows credentials for a Bot Runner. These credentials are used for automatically login (auto-login). | ||
Method | POST | PUT |
Endpoint | v1/credentialvault/external/credentials/loginsetting |
v2/credentialvault/loginsetting |
Request body changes | Not applicable | Endpoint version change |
Response body changes | Not applicable | Message displayed after successfully updating the credentials:
Credentials updated for <username>. Enterprise 11 displays this message: Credentials were successfully updated. |
Automation management API: Use this API to create automations (schedule bots), and edit and delete automations. | ||
Method | POST, PUT, and DELETE | POST, PUT, GET, and DELETE |
Endpoint | v1/schedule |
v1/schedule |
Request body changes | Not applicable | Minor change in request body to pass bot input variables |
Response body changes | Not applicable | Detailed response with bot input variable details |
User Management API: Use this API to create, edit, and delete users and roles. | ||
Method | POST, PUT, GET, and DELETE | POST, PUT, GET, and DELETE |
Endpoint | v1/usermanagement |
v1/usermanagement |
Request body changes | Not applicable | No change |
Response body changes | Not applicable | No change |
Migration API: Use this API to migrate bots from Enterprise 11 or Enterprise 10 to Automation 360 | ||
Method | GET and POST | GET and POST |
Endpoint |
|
v2/migration |
Response body changes | Not applicable |
|
Request body changes | Not applicable | Because the endpoints and request body are different, the response body is also different. |
Manual Dependency API: Use this API to add or remove a dependency (data files and such) to or from a bot. | ||
Method | POST and DELETE | Not available |
Endpoint | v1/files/manualdependencies/ |
Not available |
Request body changes | Not applicable | Not available |
Response body changes | Not applicable | Not available |
Repository Management API: Use this API to get bots and files from the Control Room repository. | ||
Method | POST, DELETE, and GET | POST, DELETE, and GET |
Endpoint | v1/repository |
v1/repository |
Request body changes | Not applicable | Additional APIs added to get folder permissions |
Response body changes | Not applicable | No change |
File Dependency API: Use this API to get the file dependency metadata to run and schedule bots. | ||
Method | GET | Not available |
Endpoint | v1/files/manualdependencies/ |
Not available |
Request body changes | Not applicable | Not available |
Response body changes | Not applicable | Not available |
Bot Lifecycle Management (BLM) API: Use this API to move (export or import) bots and dependent files across different Control Room environments. | ||
Method | POST | POST |
Endpoint | v1/blm |
v2/blm |
Request body changes | Not applicable |
|
Response body changes | Not applicable | No change |
Audit API: Use this API to get audit information about the product. | ||
Method | POST | POST |
Endpoint | v1/audit |
v1/audit |
Request body changes | Not applicable | No change |
Response body changes | Not applicable | No change |
Two-factor Authentication (2FA) API: Use this API to generate a 2FA token | ||
Method | GET and POST | Not available |
Endpoint | v1/mfa |
Not available |