AUTORO API

Name: AUTORO API API
Brand: AUTORO API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer6 EndpointsREST

For 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.

Quickstart

Get started with AUTORO 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:
"queue an AUTORO workflow for execution"

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

Capabilities

What an agent can do with AUTORO API API.

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

GET STARTED

Start building with AUTORO API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AUTORO API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use AUTORO API API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for autoro api, keeping it validated and agent-ready.

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

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

Why though Jentic?

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

Credential isolation

AUTORO API credentials are stored encrypted in the Jentic credential vault. Jentic mints the JWT at /v1/token on the agent's behalf and refreshes it transparently — the agent works only with operation responses, never with raw API credentials.

Intent-based discovery

Agents search Jentic for 'queue an AUTORO workflow' or 'cancel a session queue' and Jentic returns the matching operation with its input schema and the workflow_id parameter shape.

Time to first call

Direct AUTORO integration: half a day to wire up token minting, workflow lookup, and session queueing. Through Jentic: under thirty minutes — search, load the schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Automation 360 Control Room API

Automation 360 is an enterprise RPA platform with a richer governance and audit surface

Choose Automation 360 when audit, role management, and large bot estates matter; choose AUTORO for a lightweight queue-based trigger of cloud RPA workflows

Alternative

n8n API

n8n is an open-source workflow automation engine with code-driven nodes

Choose n8n when self-hosting and code-based extensibility matter; choose AUTORO for managed cloud RPA aimed at the Japanese market

Complementary

Zapier NLA API

Zapier can connect SaaS triggers to AUTORO via an outbound webhook step

Use Zapier as a glue layer where the trigger SaaS lives, then call AUTORO's /v1/session_queues from a Zapier custom-request step

FAQs

Specific to using AUTORO API API through Jentic.

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 at https://app.jentic.com/sign-up.

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 at https://app.jentic.com/sign-up.

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.