Celery Python API Docs | dltHub

Flower is an open-source web application for monitoring and managing Celery clusters via a REST API. The REST API base URL is http://localhost:5555/api and all requests require authentication via HTTP Basic Auth or OAuth (unless explicitly disabled).

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 add "dlt[hub]" and start loading Celery data in under 10 minutes.

---

What data can I load from Celery?

Here are some of the endpoints you can load from Celery:

---

How do I authenticate with the Celery API?

Flower supports HTTP Basic Authentication and OAuth. For Basic Auth, use a standard Authorization header with base64-encoded credentials, or the requests library's auth parameter.

1. Get your credentials

Celery does not have a native, built-in REST API for general task management. To interact with Celery via REST, users typically deploy Flower, a real-time monitoring tool for Celery. To obtain API credentials for Flower, you generally do not use a dashboard but instead configure authentication (e.g., Basic Auth or OAuth) during the Flower launch via command-line arguments like --basic_auth or by setting environment variables. If your specific application provides a wrapper API (e.g., through celery-fastapi or a custom implementation), you must retrieve or generate credentials (like API keys) through that specific application's own administrative interface or configuration files.

2. Add them to .dlt/secrets.toml

Copy
[sources.celery_source]
api_key = "your_api_key_here"
# OR if using basic auth:
# username = "your_username"
# password = "your_password"

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:

Copy
uv init
uv add "dlt[hub]"

1. Install the dlt AI harness:

Copy
uv run 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:

Copy
uv run dlthub ai toolkit install rest-api-pipeline

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 Celery 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:

Copy
uv run python celery_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline celery_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset celery_data
The duckdb destination used duckdb:/celery.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
uv run dlthub 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 /api/tasks and /api/task/result/(.+ ) from the Celery API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def celery_source(auth=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://localhost:5555/api",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": auth},
        },
        "resources": [
            {"name": "tasks", "endpoint": {"path": "api/tasks", "data_selector": "tasks"}},
            {"name": "workers", "endpoint": {"path": "api/workers", "data_selector": "workers"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="celery_pipeline",
        destination="duckdb",
        dataset_name="celery_data",
    )
    load_info = pipeline.run(celery_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):

Copy
import dlt

data = dlt.pipeline("celery_pipeline").dataset()
sessions_df = data.tasks.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM celery_data.tasks LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("celery_pipeline").dataset()
data.tasks.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 Celery data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

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.

Copy
uv run dlthub ai toolkit install data-exploration
uv run dlthub ai toolkit install dlthub-platform

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack