Birdeye Python API Docs | dltHub
Build a Birdeye-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Birdeye is a blockchain data and analytics platform accessible via REST APIs. The REST API base URL is https://public-api.birdeye.so and All requests require an API key passed in the X-API-KEY 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 pip install "dlt[workspace]" and start loading Birdeye data in under 10 minutes.
What data can I load from Birdeye?
Here are some of the endpoints you can load from Birdeye:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| token_list | /defi/tokenlist | GET | data | List of supported tokens. |
| price | /defi/price | GET | data | Current price for a token. |
| history_price | /defi/history/price | GET | data | Historical price series for a token. |
| token_overview | /defi/token_overview | GET | data | Metadata and overview information for a token. |
| token_security | /defi/token_security | GET | data | Security analysis for a token. |
| multi_price | /defi/multi-price | GET | data | Prices for multiple tokens in one call. |
| trades_by_token | /defi/txs/token | GET | data | Trade history for a specific token. |
| trades_by_pair | /defi/txs/pair | GET | data | Trade history for a token pair. |
| ohlcv_token | /defi/ohlcv | GET | data | OHLCV time‑series data for a token. |
| tokens_new_listing | /defi/v2/tokens/new_listing | GET | data | Newly listed tokens on the platform. |
| token_meta_single | /defi/v3/token/meta-data/single | GET | data | Detailed metadata for a single token. |
| markets_all | /defi/v2/markets | GET | data | Complete list of market listings. |
How do I authenticate with the Birdeye API?
Include the API key in every request header as X-API-KEY: <your_api_key>.
1. Get your credentials
- Log in to the Birdeye Dashboard.
- In the left‑hand menu select Security.
- Click Generate Key.
- Copy the newly generated API key.
- Store the key securely; it will be used as the value for the X‑API‑KEY header in all requests.
2. Add them to .dlt/secrets.toml
[sources.birdeye_source] api_key = "your_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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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 Birdeye 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:
python birdeye_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline birdeye_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset birdeye_data The duckdb destination used duckdb:/birdeye.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline birdeye_pipeline 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 token_list and price from the Birdeye 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 birdeye_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://public-api.birdeye.so", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "token_list", "endpoint": {"path": "defi/tokenlist", "data_selector": "data"}}, {"name": "price", "endpoint": {"path": "defi/price", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="birdeye_pipeline", destination="duckdb", dataset_name="birdeye_data", ) load_info = pipeline.run(birdeye_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("birdeye_pipeline").dataset() sessions_df = data.token_list.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM birdeye_data.token_list LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("birdeye_pipeline").dataset() data.token_list.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 Birdeye data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
Troubleshooting
Authentication failures
If the X‑API‑KEY header is missing or the key is invalid, the API returns 401 Unauthorized. Verify that the header is present and the key is active.
Rate limits
When the usage exceeds the allowed quota, the API responds with 429 Too Many Requests. The dashboard shows current usage; implement exponential backoff and retry after a short delay.
Pagination quirks
List endpoints often return paginated results with parameters such as limit, offset, or page. The response includes pagination metadata (e.g., next, total). Follow the next token or increment the offset to retrieve subsequent pages.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Birdeye?
Request dlt skills, commands, AGENT.md files, and AI-native context.