How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

automation-anywhere Files API

Manage individual bot files and their dependencies in the repository

automation-anywhere Files API is one of 22 APIs that Automation Anywhere publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include File. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 3 JSON Schemas.

This API exposes 9 operations across 9 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 2019.

Requests are made against a single base URL, https://{controlRoomUrl}/orchestrator/v1/hotbot.

9 operations 9 paths 13 schemas 1 DELETE3 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2019
Base URL
https://automationanywhere-be-prod.automationanywhere.com
Authentication
HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

automation-anywhere Files API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as X-Authorization (xAuthorization). By default, every request must be authenticated.

  • bearerAuth — JWT token obtained from the Authentication API
  • xAuthorization — JWT token obtained from the Authentication API

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 1 DELETE, 3 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Files 9

Manage individual bot files and their dependencies in the repository

POST
/file/list
List files in the repository
listFiles body → 200400401
GET
/files/{fileid}/content
Download file contents
downloadFile 1 param → 200401404
GET
/files/{fileid}/dependencies
View file dependencies
getFileDependencies 1 param → 200401404
PUT
/files/{fileid}/dependencies/{workspaceId}
Update manual file dependencies
updateFileDependencies 2 params body → 200400401404
GET
/files/{fileid}/parents
Get file parent folders
getFileParents 1 param → 200401404
DELETE
/files/{id}
Delete a file
deleteFile 1 param → 200401404
POST
/files/packagesVersionUpdate
Update package versions
updatePackageVersions body → 200400401
POST
/files/version/assignLabel
Assign production label to bot version
assignVersionLabel body → 200400401404
POST
/recover
Recover bots from deleted user repository
recoverBots body → 200400401

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are RepositoryObject (13 properties), ObjectPermission (6 properties), PackageVersionUpdateRequest (3 properties), FilterRequest (3 properties). Each schema is shown below with its type and property counts.

Error
object
Standard error response
2 properties
FilterRequest
object
Generic filter and pagination request for list endpoints
3 properties
PageRequest
object
Pagination parameters
2 properties
RecoverRequest
object
Payload to recover bots from a deleted user's private workspace
2 properties 1 required
ObjectPermission
object
Actions the current user can perform on a repository object
6 properties
AssignLabelRequest
object
Payload to assign the production label to a specific bot version
2 properties 2 required
PageInfo
object
Pagination metadata
3 properties
RepositoryObject
object
A file or folder in the Control Room repository
13 properties
FileParentsResponse
object
Parent folder information for a repository object
1 property
DependencyUpdateRequest
object
Payload to update manual dependencies for a file
1 property
FileListResponse
object
Paginated list of repository objects
2 properties
PackageVersionUpdateRequest
object
Payload to trigger package version updates on bot files
3 properties
FileDependencyResponse
object
Dependency information for a bot file
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

automation-anywhere-files-api-openapi.yml Raw ↑

Other APIs Automation Anywhere publishes across the network.

Automation Anywhere Package SDK
automation-anywhere AccessDetails API
automation-anywhere Allocations API
automation-anywhere AttributeValues API
automation-anywhere AuditData API
automation-anywhere Authentication API
automation-anywhere BotRunData API
automation-anywhere Credentials API
automation-anywhere Deployments API
automation-anywhere Folders API
automation-anywhere LockerConsumers API
automation-anywhere LockerMembers API
Where this information came from

This is an independent, third-party profile of automation-anywhere Files API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.