Neynar Farcaster Python API Docs | dltHub

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

Last updated:

Neynar provides APIs for interacting with the Farcaster decentralized social protocol, allowing querying of user data and social graphs. The API supports mini apps and on-chain events. Essential endpoints include fetching user actions and signers by FID. The REST API base URL is https://api.neynar.com and All requests require an API key provided via the x-api-key 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 pip install "dlt[workspace]" 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:

ResourceEndpointMethodData selectorDescription
users/v2/farcaster/user/bulk?fids=GETusersBulk fetch users by FIDs (response contains a "users" array).
feed/v2/farcaster/feed/following?fid=&limit=GETcastsFetch a user's following feed (response contains a "casts" array).
casts_bulk/v2/farcaster/cast/bulk?hashes=GETcastsBulk fetch casts by hashes (response contains a "casts" array).
casts_by_hash/v2/farcaster/cast?hash=GETFetch a single cast by hash (response is a top‑level cast object).
signer_lookup/v2/farcaster/signer/lookup?public_key=GETsignersLookup signer(s) by public key (response contains a "signers" array).

How do I authenticate with the Neynar Farcaster API?

Include your Neynar API key in the x-api-key header for every request (e.g., 'x-api-key: YOUR_KEY').

1. Get your credentials

  1. Visit https://neynar.com or the Developer Portal (https://dev.neynar.com).
  2. Sign up / sign in and go to the Developer / API keys section.
  3. Create or subscribe to an API plan; the portal will provision a NEYNAR_API_KEY.
  4. Copy the API key and store it securely (use a secrets manager).

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

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:

dlt pipeline neynar_farcaster_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 users and feed 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, }, }, "resources": [ {"name": "users", "endpoint": {"path": "v2/farcaster/user/bulk?fids=<fids>", "data_selector": "users"}}, {"name": "feed", "endpoint": {"path": "v2/farcaster/feed/following?fid=<fid>&limit=<n>", "data_selector": "casts"}} ], } 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.users.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM neynar_farcaster_data.users LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("neynar_farcaster_pipeline").dataset() data.users.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:

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 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 Neynar Farcaster?

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