Automation Anywhere Python API Docs | dltHub
Build a Automation Anywhere-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Automation Anywhere Control Room API is a RESTful interface for managing and administering the Automation 360 RPA platform. The REST API base URL is https://<your_control_room_url> and All requests require either an X-Authorization header or an Authorization Bearer header..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Automation Anywhere data in under 10 minutes.
What data can I load from Automation Anywhere?
Here are some of the endpoints you can load from Automation Anywhere:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| repository_files | /v1/repository/filefolder/list | POST | list | Returns a list of files and folders in a directory. |
| audit_logs | /v1/audit/list | POST | list | Returns audit data for specified filters. |
| users | /v1/usermanagement/users/list | POST | list | Returns a list of users. |
| queues | /v2/wlm/queues/list | POST | Returns a list of all available workload queues. | |
| licenses | /v2/license | GET | Returns detailed license information. |
How do I authenticate with the Automation Anywhere API?
All requests must include either an 'X-Authorization' header with the JWT token or an 'Authorization' header with a 'Bearer ' value. Note that 'Authorization: Bearer' is supported as of Automation 360 v.27 and later.
1. Get your credentials
- Log in to the Automation Anywhere Control Room as an administrator. 2. Navigate to Administration > Roles and ensure the target user has a role with the 'Generate API-Key' permission enabled. 3. Log in as the user assigned this role. 4. Click the user profile icon (usually bottom-left) and select 'My settings'. 5. Click the 'Generate API-Key' button to create the key and copy it to your clipboard.
2. Add them to .dlt/secrets.toml
[sources.automation_anywhere_source] api_key = "REPLACE_ME"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI harness:
dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlthub ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Automation Anywhere API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python automation_anywhere_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline automation_anywhere_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset automation_anywhere_data The duckdb destination used duckdb:/automation_anywhere.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline automation_anywhere_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads /v2/authentication and /v2/credentialvault/credentials from the Automation Anywhere API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def automation_anywhere_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<your_control_room_url>", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "repository_files", "endpoint": {"path": "v1/repository/filefolder/list", "data_selector": "list"}}, {"name": "users", "endpoint": {"path": "v1/usermanagement/users/list", "data_selector": "list"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="automation_anywhere_pipeline", destination="duckdb", dataset_name="automation_anywhere_data", ) load_info = pipeline.run(automation_anywhere_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("automation_anywhere_pipeline").dataset() sessions_df = data.repository_files.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM automation_anywhere_data.repository_files LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("automation_anywhere_pipeline").dataset() data.repository_files.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Automation Anywhere data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install
Was this page helpful?
Community Hub
Need more dlt context for Automation Anywhere?
Request dlt skills, commands, AGENT.md files, and AI-native context.