Neynar Farcaster Python API Docs | dltHub
Build a Neynar Farcaster-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Neynar is a provider of Farcaster APIs for interacting with the decentralized social protocol to query user data, social graphs, and on-chain events. The REST API base URL is https://api.neynar.com and all requests require an API key in a custom HTTP 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 Neynar Farcaster data in under 10 minutes.
What data can I load from Neynar Farcaster?
Here are some of the endpoints you can load from Neynar Farcaster:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| user_search | /v2/farcaster/user/search?q={q} | GET | result | Search for usernames |
| channel_list | /v2/farcaster/channel/list | GET | channels | Fetch all channels with their details |
| user_followers | /v2/farcaster/user/followers?fid={fid} | GET | users | Fetch a list of followers for a specific FID |
| user_notifications | /v2/farcaster/notifications?fid={fid} | GET | notifications | Returns a list of notifications for a specific FID |
| user_casts | /v2/farcaster/feed/user/casts?fid={fid} | GET | casts | Fetch casts for a given user FID |
How do I authenticate with the Neynar Farcaster API?
All requests must include an API key in the 'x-api-key' HTTP header. HTTPS is required for all requests.
1. Get your credentials
- Navigate to the Neynar Developer Portal at https://dev.neynar.com and sign in with your account.\n2. Navigate to the Developer / API keys section.\n3. Ensure you have an active subscription; if not, subscribe to an API plan.\n4. Once the subscription is active, the portal will provision your NEYNAR_API_KEY.\n5. Copy the key and store it securely in a secrets manager or environment variable.
2. Add them to .dlt/secrets.toml
[sources.neynar_farcaster_source] api_key = "your_neynar_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 Neynar Farcaster 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 neynar_farcaster_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline neynar_farcaster_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset neynar_farcaster_data The duckdb destination used duckdb:/neynar_farcaster.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 /v2/farcaster/user/bulk and /v2/farcaster/feed/following from the Neynar Farcaster 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 neynar_farcaster_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.neynar.com", "auth": {"type": "api_key", "api_key": api_key, "name": "x-api-key", "location": "header"}, }, "resources": [ {"name": "user_search", "endpoint": {"path": "v2/farcaster/user/search", "data_selector": "result"}}, {"name": "channel_list", "endpoint": {"path": "v2/farcaster/channel/list", "data_selector": "channels"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="neynar_farcaster_pipeline", destination="duckdb", dataset_name="neynar_farcaster_data", ) load_info = pipeline.run(neynar_farcaster_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("neynar_farcaster_pipeline").dataset() sessions_df = data.user_search.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM neynar_farcaster_data.user_search LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("neynar_farcaster_pipeline").dataset() data.user_search.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 Neynar Farcaster 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.
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 Neynar Farcaster?
Request dlt skills, commands, AGENT.md files, and AI-native context.