dagu-rest-api

Included with Lifetime

$97 forever

Guide for using the Dagu REST API. Use when programmatically managing workflows, querying execution status, or integrating Dagu with external systems.

Backend & APIs

What this skill does


# Dagu REST API

Use this skill when integrating Dagu with external systems, automating workflow operations, or programmatically managing workflows through the API.

## When to Use This Skill

Activate when:
- Triggering workflows programmatically
- Querying workflow status from applications
- Building automation around Dagu
- Integrating Dagu with CI/CD pipelines
- Creating custom dashboards or monitoring tools
- Scheduling workflows dynamically
- Fetching execution logs programmatically

## Core API Capabilities

The Dagu REST API provides endpoints for:

1. **Workflow Operations** - Start, stop, retry workflows
2. **Status Queries** - Get workflow and execution status
3. **DAG Management** - List and inspect workflow definitions
4. **Execution History** - Query past executions
5. **Log Retrieval** - Fetch execution logs

## Base URL

Default API base URL: `http://localhost:8080/api/v1`

Configure in Dagu settings if using a different host/port.

## Authentication

Consult `references/authentication.md` for details on:
- API token configuration
- Authentication headers
- Security best practices

## Quick Start Operations

### Start a Workflow

```bash
POST /dags/{dagName}/start
```

Basic example:
```bash
curl -X POST http://localhost:8080/api/v1/dags/my_workflow/start
```

For parameter passing and advanced options, see `references/workflow-operations.md`.

### Get Workflow Status

```bash
GET /dags/{dagName}/status
```

Returns current status, running steps, and execution details.

### Stop a Workflow

```bash
POST /dags/{dagName}/stop
```

Stops currently running execution.

## When to Consult References

- **Detailed endpoint documentation**: Read `references/api-endpoints.md`
- **Workflow operations (start/stop/retry)**: Read `references/workflow-operations.md`
- **Status and monitoring queries**: Read `references/status-queries.md`
- **Authentication setup**: Read `references/authentication.md`
- **Integration examples**: Read `references/integration-examples.md`
- **Error handling**: Read `references/error-handling.md`

## Common Use Cases

### CI/CD Integration

Trigger Dagu workflows from your CI/CD pipeline:

```bash
# In GitHub Actions, GitLab CI, etc.
curl -X POST http://dagu-server:8080/api/v1/dags/deploy_production/start \
  -H "Content-Type: application/json" \
  -d '{"params": "VERSION=1.2.3 ENVIRONMENT=production"}'
```

For complete CI/CD integration patterns, see `references/integration-examples.md`.

### Monitoring and Alerting

Query workflow status for external monitoring:

```bash
# Check if workflow is running
curl http://localhost:8080/api/v1/dags/critical_job/status
```

Build custom alerts based on status responses. See `references/status-queries.md` for response format details.

### Dynamic Scheduling

Trigger workflows based on external events:

```python
import requests

def trigger_workflow(dag_name, params=None):
    url = f"http://localhost:8080/api/v1/dags/{dag_name}/start"
    data = {"params": params} if params else {}
    response = requests.post(url, json=data)
    return response.json()
```

For comprehensive examples in multiple languages, see `references/integration-examples.md`.

## Response Formats

All API responses are JSON. Common response structure:

```json
{
  "status": "success",
  "data": { ... }
}
```

Error responses:
```json
{
  "status": "error",
  "message": "Error description"
}
```

For complete response schemas, consult `references/api-endpoints.md`.

## Key Principles

- **RESTful design**: Standard HTTP methods (GET, POST, DELETE)
- **JSON responses**: All responses in JSON format
- **Idempotent operations**: Safe to retry most operations
- **Error codes**: Standard HTTP status codes
- **Stateless**: Each request is independent

## Pro Tips

- Use the API for automation, use Web UI for manual operations
- Implement retry logic for network failures
- Cache DAG lists if querying frequently
- Use webhooks for event-driven workflows when possible
- Monitor API response times for performance issues
- Validate workflow names before calling API to avoid errors

Files: 2

Size: 10.4 KB

Complexity: 23/100

Category: Backend & APIs

Source: https://github.com/vinnie357/claude-skills/tree/main/plugins/tools/dagu/skills/rest-api

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts