Argilla Python API Docs | dltHub

Build a Argilla-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Argilla is a FastAPI-based platform for managing data for AI, including datasets, records, and training feedback loops for LLMs and other models. The REST API base URL is http://localhost:6900 and supports both API key and Bearer token authentication schemes.

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 Argilla data in under 10 minutes.


What data can I load from Argilla?

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

ResourceEndpointMethodData selectorDescription
workspaces/api/v1/me/workspacesGETList workspaces for the current user
workspaces/api/v1/workspaces/{workspace_id}GETGet a specific workspace
datasets/api/v1/datasetsGETList all datasets
dataset_records/api/v1/datasets/{dataset_id}/recordsGETList records for a dataset
me_records/api/v1/me/datasets/{dataset_id}/recordsGETList current user's records for a dataset

How do I authenticate with the Argilla API?

The API supports authentication using an API key passed in the 'X-Argilla-Api-Key' header, or Bearer token authentication via the 'Authorization' header.

1. Get your credentials

To obtain your Argilla API key, log in to your Argilla instance UI and navigate to the "My Settings" page. Your API key will be displayed there, where you can copy it for use in your applications. If you have deployed Argilla via Hugging Face Spaces, you can also click "Import from the SDK" on the home page to see a code snippet containing your API URL and key. If you are running Argilla locally via Docker, the default API key is often set to 'argilla.apikey' (though this should be changed for production).

2. Add them to .dlt/secrets.toml

[sources.argilla_source] api_url = "https://your-argilla-instance.url" api_key = "your_actual_api_key_here"

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:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

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:

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

uv run python argilla_pipeline.py

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

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

Inspect your pipeline and data:

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 /me/datasets and /workspaces from the Argilla API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def argilla_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:6900", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "dataset_records", "endpoint": {"path": "datasets/{dataset_id}/records", "data_selector": "items"}}, {"name": "me_records", "endpoint": {"path": "me/datasets/{dataset_id}/records", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="argilla_pipeline", destination="duckdb", dataset_name="argilla_data", ) load_info = pipeline.run(argilla_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):

import dlt data = dlt.pipeline("argilla_pipeline").dataset() sessions_df = data.dataset_records.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM argilla_data.dataset_records LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("argilla_pipeline").dataset() data.dataset_records.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 Argilla data to?

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

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

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.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Argilla?

Request dlt skills, commands, AGENT.md files, and AI-native context.