Feast Python API Docs | dltHub

Feast is an open-source feature store that provides a REST API server for low-latency feature retrieval and data ingestion operations. The REST API base URL is http://localhost:6566 and all requests require a Bearer token in the Authorization header.

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

---

What data can I load from Feast?

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

---

How do I authenticate with the Feast API?

The REST API supports Bearer token authentication, which must be provided in the 'Authorization' header with the format 'Bearer '. Feast does not provide built-in authentication, so it is the client's responsibility to manage and pass these tokens to the Feast server.

1. Get your credentials

Feast does not provide a centralized dashboard for generating static API keys. Instead, the Feast Registry and Feature Servers support Bearer token authentication. To obtain credentials, you must configure your identity provider or authentication backend as defined in your specific infrastructure deployment. Once you have a valid token, include it in your HTTP requests using the Authorization header: Authorization: Bearer . If your server is running in a managed environment, refer to your organization's documentation to retrieve the appropriate token.

2. Add them to .dlt/secrets.toml

Copy
[sources.feast_source]
api_token = "your_bearer_token_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:

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 Feast 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 feast_pipeline.py

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

Copy
Pipeline feast_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset feast_data
The duckdb destination used duckdb:/feast.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 /get-online-features and /push from the Feast 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 feast_source(auth=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://localhost:6566",
            "auth": {"type": "bearer", "token": auth},
        },
        "resources": [
            {"name": "entities", "endpoint": {"path": "api/v1/entities"}},
            {"name": "feature_tables", "endpoint": {"path": "api/v1/feature-tables"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="feast_pipeline",
        destination="duckdb",
        dataset_name="feast_data",
    )
    load_info = pipeline.run(feast_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("feast_pipeline").dataset()
sessions_df = data.entities.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM feast_data.entities LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("feast_pipeline").dataset()
data.entities.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 Feast 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