canonical: https://jentic.com/apis/autoro.io/autoro

# AUTORO API

Jentic publishes the only available OpenAPI specification for AUTORO API, keeping it validated and agent-ready. AUTORO (formerly Robotic Crowd) is a cloud-based RPA platform aimed at Japanese-market business automation. The public API is intentionally narrow - six endpoints covering token generation, workflow listing and detail retrieval, and session-queue management - so that callers can list available workflows, queue them for execution, and cancel queued sessions without having to model the full authoring surface. The bearer token issued at `/v1/token` authorises every other call.

## For AI agents

Mint a JWT, list AUTORO workflows, queue a workflow for execution by adding it to a session queue, and cancel queued sessions. Useful for triggering RPA workflows from external systems.

## Scope

Does not handle workflow authoring, runner provisioning, or per-step debugging - use for queueing AUTORO workflow runs and managing session queues only.

## Capabilities

- Mint a JWT for API access via POST `/v1/token`
- List all workflows visible to the calling account with GET `/v1/workflows`
- Retrieve detail (steps, parameters) for a specific workflow via GET `/v1/workflows/{workflow_id}`
- Queue a workflow for execution by creating a session queue entry with POST `/v1/session_queues`
- Cancel a queued session that has not yet started via DELETE `/v1/session_queues/{session_queue_id}/cancel`
- Inspect outstanding session queues with GET `/v1/session_queues`

## Use cases

### Trigger an RPA workflow from a SaaS event

Wire a SaaS event (a new row in a database, a Slack command, a CRM stage change) to an AUTORO workflow run. The integration mints a JWT at `/v1/token`, calls GET `/v1/workflows` to confirm the target workflow ID, and POST `/v1/session_queues` to queue it. Cancellation is one DELETE call away if the upstream event is later retracted.

Example prompt: POST `/v1/session_queues` with the workflow_id matching the SaaS event, then poll `/v1/session_queues` to confirm queue placement

### Workflow inventory dashboard

Build a dashboard that lists every AUTORO workflow available to a department alongside its parameters and last run timing. GET `/v1/workflows` feeds the list and GET `/v1/workflows/{workflow_id}` fetches the detail per row. Refreshing daily is enough because workflows do not change frequently and avoids hitting the API for every dashboard view.

Example prompt: GET `/v1/workflows` for the listing, then iterate GET `/v1/workflows/{workflow_id}` to populate the detail panel

### Agent-driven RPA invocation

An AI agent given a business task selects the right AUTORO workflow from the catalogue and queues it. The agent searches Jentic for the action, looks up the matching workflow_id from `/v1/workflows`, and POSTs to `/v1/session_queues.` Through Jentic the JWT lifecycle is handled inside the credential vault, so the agent does not need to mint or refresh tokens manually.

Example prompt: Identify the workflow_id by name, then POST `/v1/session_queues` with that workflow_id and any required parameters

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/token` | Mint a JWT from API credentials |
| GET | `/v1/workflows` | List all workflows |
| GET | `/v1/workflows/{workflow_id}` | Get detail for a specific workflow |
| POST | `/v1/session_queues` | Queue a workflow for execution |
| GET | `/v1/session_queues` | List session queues |
| DELETE | `/v1/session_queues/{session_queue_id}/cancel` | Cancel a queued session |

## Key resources

- **Authentication** — Mint JWTs for API access
- **Workflows** — List and inspect AUTORO workflows
- **Session Queues** — Queue workflow runs and cancel pending sessions

## Why Jentic

- **Setup:** Wiring the AUTORO API by hand means minting a JWT at POST `/v1/token`, refreshing it before it expires, and carrying it in the Authorization header on every workflow and session-queue call. Through Jentic you install once, import the AUTORO API from the API Directory, store your AUTORO API credentials once, and your agent calls it.
- **Permission scoping:** AUTORO passes the workflow_id when queuing a run in the request body, so scope your agent to the operations it needs: for example allow GET `/v1/workflows` and POST `/v1/session_queues` to list and queue workflow runs. You choose the operations it may call, so cancelling a queued session with DELETE `/v1/session_queues/{session_queue_id}/cancel` is not included unless you add it.
- **Credential handling:** Your AUTORO API credentials are stored once, encrypted, by your own Jentic One instance and the JWT is minted server-side at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'queue an AUTORO workflow for execution' or 'cancel a queued AUTORO session', and Jentic returns the matching operation like POST `/v1/session_queues` with its workflow_id input schema so the agent calls it without reading the AUTORO developer reference.

## Related APIs

- **Automation 360 Control Room API** — Automation 360 is an enterprise RPA platform with a richer governance and audit surface
- **n8n API** — n8n is an open-source workflow automation engine with code-driven nodes
- **Zapier NLA API** — Zapier can connect SaaS triggers to AUTORO via an outbound webhook step

## FAQ

### Why is there no official OpenAPI spec for AUTORO API?

AUTORO publishes a developer reference at developer.autoro.io but no downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AUTORO API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the AUTORO API use?

AUTORO uses bearer tokens. POST `/v1/token` mints a JWT from your API credentials and every subsequent call carries the JWT in the Authorization header. Through Jentic the credentials are held in the vault and JWTs are minted server-side.

### How do I queue a workflow run with the AUTORO API?

Mint a JWT at `/v1/token`, find the workflow_id via GET `/v1/workflows`, and POST `/v1/session_queues` with the workflow_id (and any parameters the workflow needs). The response carries a session_queue_id you can use to cancel via DELETE `/v1/session_queues/{session_queue_id}/cancel.`

### How do I cancel a queued AUTORO session through Jentic?

Search Jentic for 'cancel an AUTORO session', load DELETE `/v1/session_queues/{session_queue_id}/cancel`, and execute it with the session_queue_id you stored when the session was queued. Get started with Jentic One, the self-hosted execution layer.

### Can I see the steps inside an AUTORO workflow via the API?

GET `/v1/workflows/{workflow_id}` returns workflow detail including the steps and parameters. The authoring of steps is done in the AUTORO console; the API exposes them read-only for inspection and parameter discovery.

### What are the rate limits for the AUTORO API?

AUTORO sets per-plan throughput limits in the customer dashboard rather than the OpenAPI spec. Token minting is lightweight, but `/v1/session_queues` is bounded by the runner concurrency on your plan; check https://developer.autoro.io for current limits.

### Can I limit what my agent is allowed to do with the AUTORO API?

Yes. Because Jentic One is self-hosted, you decide which AUTORO operations your agent may call, so you can allow GET `/v1/workflows` and POST `/v1/session_queues` to let it list and queue workflow runs while withholding everything else. A destructive call like DELETE `/v1/session_queues/{session_queue_id}/cancel` is not available to the agent unless you explicitly add it. Your rules govern which operations and credentials the agent uses, so it can queue a run without being able to cancel one or inspect workflow detail.