Automation 360 Control Room API

Name: Automation 360 Control Room API API
Brand: Automation 360 Control Room API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer16 EndpointsREST

For Agents

Authenticate with a Control Room user, then deploy bots, schedule runs, manage users, roles, and credentials, query audit logs, and inspect devices and workload queues — the full Control Room surface as a tool list.

Quickstart

Get started with Automation 360 Control Room API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"deploy an Automation 360 bot to a runner"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Automation 360 Control Room API API.

Authenticate with username and password (or API key) via POST /authentication and refresh tokens at /authentication/token

Deploy a bot to a runner via POST /automations/deploy with a bot file ID and target devices

Schedule recurring bot runs via POST /schedule/automations

List bots, activities, and workload queues using POST /repository/files/list, /activity/list, and /workload/queues/list

GET STARTED

Start building with Automation 360 Control Room API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Automation 360 Control Room API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Automation 360 Control Room API, keeping it validated and agent-ready. Automation 360 is Automation Anywhere's RPA platform, and the Control Room API is the programmatic surface for everything that runs inside a Control Room: bots, deployments, schedules, devices, users, roles, audit logs, the credential vault, and workload queues. Most listing endpoints use POST with a JSON filter body rather than GET so callers can express complex multi-field filters and pagination in one request. Authentication is a bearer token issued by /authentication and refreshed via /authentication/token.

Use Cases

Patterns agents use Automation 360 Control Room API API for, with concrete tasks.

★ CI/CD-style bot deployment

Treat Automation 360 bots like build artefacts: a CI pipeline authenticates with /authentication, lists the bot file in /repository/files/list to confirm the version, and POSTs to /automations/deploy with the chosen runner device. Activity status is then polled via /activity/list. This replaces manual Control Room clicks with a reproducible, audit-friendly pipeline.

After authenticating, POST /automations/deploy with fileId and runAsUserIds to launch the bot, then poll /activity/list for the deployment's status

Scheduled batch run governance

An ops team manages overnight RPA workloads through the API instead of the UI. /schedule/automations creates each cron-like schedule, /workload/queues/list reports queue depth, and /audit/list provides the trail compliance reviewers need. When a runner fails, the team uses /devices/list to pivot to a healthy runner and re-deploy.

POST /schedule/automations with a cron expression and a target bot file, then poll /workload/queues/list to confirm executions land in the queue

Compliance and audit reporting

Compliance teams pull Control Room audit data into a SIEM by calling POST /audit/list with a date range and event-type filter, then storing the result for retention. Pairing this with /usermanagement/users/list and /usermanagement/roles/list makes user-access reviews routine: identify who held which role on a given date and what they did during that window.

POST /audit/list with filter on user_id and a date range, then export the results to the compliance store

Agent-driven operational triage

An on-call AI agent investigating a failed automation can list recent activity, find the failed run, and inspect the device and the user that launched it — all via the Control Room API. Through Jentic the bearer token lifecycle is managed inside the credential vault, so the agent does not need to call /authentication or /authentication/token directly.

List recent activities, identify the failed run, then GET /usermanagement/users/{userId} and /devices/list to gather context for the on-call summary

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for automation 360 control room api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/authentication

Authenticate and obtain a bearer token

POST

/automations/deploy

Deploy a bot to a runner

POST

/schedule/automations

Create a schedule for a bot

POST

/repository/files/list

List bots in the repository

POST

/activity/list

List bot activities

POST

/audit/list

Query Control Room audit logs

POST

/usermanagement/users/list

List Control Room users

POST

/credentialvault/credentials/list

List credential vault entries

POST

/authentication

Authenticate and obtain a bearer token

POST

/automations/deploy

Deploy a bot to a runner

POST

/schedule/automations

Create a schedule for a bot

POST

/repository/files/list

List bots in the repository

POST

/activity/list

List bot activities

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Automation 360 usernames, passwords, and API keys are stored encrypted in the Jentic credential vault. Jentic calls /authentication and /authentication/token server-side, so agents only ever work with short-lived bearer tokens scoped to the request.

Intent-based discovery

Agents search Jentic for intents like 'deploy a bot' or 'query Control Room audit logs' and Jentic returns the matching POST endpoint with its filter schema, so the agent does not need to navigate the Control Room HTML docs.

Time to first call

Direct Automation 360 integration: 2-4 days to model the token lifecycle, POST-with-filter-body listing pattern, and audit pagination. Through Jentic: under an hour — search, load the schema for each operation, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

n8n API

n8n is an open-source workflow automation tool with a similar deploy and run surface

Choose n8n for code-driven, open-source workflow automation; choose Automation 360 when the workload needs UI-driven RPA with credential vault and bot governance

Alternative

Zapier NLA API

Zapier offers SaaS-to-SaaS automation without the enterprise governance layer

Choose Zapier for lightweight SaaS connections; choose Automation 360 for desktop, mainframe, and on-prem RPA with audit and role management

Complementary

ServiceNow API

ServiceNow tickets often trigger Automation 360 bot runs

Use ServiceNow as the system of record for incidents and Automation 360 for the bot that resolves them, calling /automations/deploy from a ServiceNow workflow

FAQs

Specific to using Automation 360 Control Room API API through Jentic.

Why is there no official OpenAPI spec for Automation 360 Control Room API?

Automation Anywhere publishes HTML reference docs but not a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Automation 360 Control Room API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Automation 360 Control Room API use?

The Control Room issues a bearer token from POST /authentication when called with a username and password (or apiKey). Refresh the token at POST /authentication/token before it expires. Through Jentic the username and password are held in the credential vault and the bearer token is minted server-side per call.

How do I deploy a bot through the Automation 360 Control Room API?

After authenticating, list the bot file with POST /repository/files/list, take its fileId, and POST /automations/deploy with the fileId and an array of runAsUserIds. Track the resulting deployment via POST /activity/list filtered on the returned deployment id.

Can I query Control Room audit logs through the API?

Yes. POST /audit/list accepts filter criteria such as date range, user, and event type, and returns paginated audit entries. This is the route compliance teams use to feed Control Room audit data into a SIEM.

How do I schedule a bot run through Jentic?

Search Jentic for 'schedule a bot run', load POST /schedule/automations, and execute it with a cron expression and the target bot's fileId. Jentic mints the bearer token from your stored Control Room credentials. Get started at https://app.jentic.com/sign-up.

What are the rate limits for the Automation 360 Control Room API?

Automation Anywhere does not document fixed rate limits in the spec; throughput depends on Control Room sizing and concurrent runner capacity. Treat list endpoints as throttled and use the filter body to narrow results rather than polling broadly.