Waymark / Routes / airflow.apache.org Trigger Airflow DAG run via stable REST API
domain: airflow.apache.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Ensure Airflow 2.x is running with the REST API enabled; the stable API is available at /api/v1/ by default. Authenticate: obtain a session or use HTTP Basic Auth credentials passed in the Authorization header for each request. Send a POST request to /api/v1/dags/{dag_id}/dagRuns with a JSON body containing at minimum a logical_date or conf object. Inspect the response body: a 200 or 409 status with a dag_run_id field confirms the run was created or already exists. Poll GET /api/v1/dags/{dag_id}/dagRuns/{dag_run_id} until the state field is one of success, failed, or upstream_failed. Retrieve task-instance logs if needed via GET /api/v1/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances. Known gotchas The stable REST API requires auth_backend to be set; if it is set to deny_all the endpoint returns 403 even with valid credentials. Supplying a logical_date that already exists for the DAG returns a 409 Conflict; use a unique timestamp or omit the field to let Airflow assign one. The DAG must not be paused; a paused DAG ignores trigger requests — unpause it first via PATCH /api/v1/dags/{dag_id} with {is_paused: false}.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp