canonical: https://jentic.com/apis/rundeck.com/rundeck

# Rundeck API

Rundeck API for job scheduling and runbook automation. Provides endpoints for managing jobs, executions, projects, system configuration, storage, users, and metrics. The API exposes 74 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list the jobs that exist for a project, run the specified job. Covers 74 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- List the jobs that exist for a project
- Run the specified job
- Delete all job executions
- Retry a failed job execution on failed nodes only or on the same as the executio
- Export a single job definition in XML or YAML formats.

## Use cases

### HR and Recruiting Operations

Use the Rundeck API to perform hr recruiting operations programmatically. The API provides 74 endpoints covering core functionality including list the jobs that exist for a project, run the specified job, list job executions.

Example prompt: Call GET `/api/26/project/{project}/jobs` to list the jobs that exist for a project

### Automated 26 Management

Automate 26 operations by combining multiple Rundeck API endpoints. Agents can run the specified job and then list job executions in a single workflow.

Example prompt: Call POST `/api/26/job/{id}/executions` to run the specified job, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rundeck API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'list the jobs that exist for a project', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/26/project/{project}/jobs` | List the jobs that exist for a project |
| POST | `/api/26/job/{id}/executions` | Run the specified job |
| GET | `/api/26/job/{id}/executions` | List job executions |
| DELETE | `/api/26/job/{id}/executions` | Delete all job executions |
| POST | `/api/26/job/{jobID}/retry/{executionID}` | Retry a failed job execution on failed nodes only or on the same as the executio |
| GET | `/api/26/job/{id}` | Export a single job definition in XML or YAML formats. |
| DELETE | `/api/26/job/{id}` | Delete a single job definition. |
| GET | `/api/26/job/{id}/info` | Get metadata about a specific job. |

## Key resources

- **26** — Operations for 26
- **34** — Operations for 34

## Why Jentic

- **Setup:** Wiring Rundeck by hand means passing your key in the X-Rundeck-Auth-Token header and resolving the {rundeck_host} base against your own server for each job call. Through Jentic you install once, import Rundeck from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Rundeck puts the project and job ids in the URL path (`/project/{project}/jobs`, `/job/{id}/executions`), so a rule can pin your agent to one project: it can list and run jobs there and nothing else. You choose the operations it may call, so deleting all job executions is not included unless you add it.
- **Credential handling:** Your Rundeck auth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list a project's jobs' or 'run a job', and Jentic returns the matching Rundeck operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Rundeck API use?

The Rundeck API uses an API key passed in the `X-Rundeck-Auth-Token` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list the jobs that exist for a project with the Rundeck API?

Yes. Use the GET `/api/26/project/{project}/jobs` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list the jobs that exist for a project through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list the jobs that exist for a project'. Jentic returns the matching Rundeck API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Rundeck API have?

The Rundeck API exposes 74 endpoints covering 26, 34 operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Rundeck operations and credentials the agent may use. Since Rundeck puts the project and job ids in the URL path, such as `/project/{project}/jobs` and `/job/{id}/executions`, you can pin the agent to a single project so it only lists and runs jobs there. Destructive calls like deleting all job executions stay out of scope unless you explicitly grant them.