Skip to content
Communication/messaging

apache.org:airflow

Airflow API (Stable) sandbox and mock API

# Overview To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases. Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: applicati Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
73
Collections
-
Event types
-
Start this simulation
example request
curl https://your-apache-airflow.slurry.io/api/v1/config \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.5.1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 73.

  • GET/config
  • GET/connections
  • POST/connections
  • POST/connections/test
  • GET/connections/{connection_id}
  • PATCH/connections/{connection_id}
  • DELETE/connections/{connection_id}
  • GET/dagSources/{file_token}
  • GET/dagWarnings
  • GET/dags
  • PATCH/dags
  • GET/dags/{dag_id}