Twitter Python API Docs | dltHub
Build a Twitter-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
X (Twitter) API v2 provides programmatic access to posts, users, spaces, lists, and other platform data through REST endpoints. The REST API base URL is https://api.x.com/2 and 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 Twitter data in under 10 minutes.
What data can I load from Twitter?
Here are some of the endpoints you can load from Twitter:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| tweets | 2/tweets | GET | data | Retrieve specific Tweets by ID |
| users | 2/users | GET | data | Retrieve specific Users by ID |
| lists | 2/lists | GET | data | Retrieve details of specific Lists |
| recent_search | 2/tweets/search/recent | GET | data | Retrieve Tweets from the last 7 days |
| bookmarks | 2/users/{id}/bookmarks | GET | data | Retrieve the bookmarked Tweets of a user |
How do I authenticate with the Twitter API?
Requests require an Authorization header with the Bearer scheme followed by the token string, formatted as 'Authorization: Bearer '.
1. Get your credentials
- Navigate to the X Developer Console at console.x.com and sign in with your X account.
- Accept the Developer Agreement and provide details about your intended use case.
- Create a new App within a Project to serve as a container for your credentials.
- Once the app is created, navigate to the Keys and tokens page.
- Click 'Generate' or 'Regenerate' to obtain your API Key, API Secret, and Bearer Token. Note: Some credentials (like secrets) are shown only once, so store them immediately in a secure location.
- If your use case requires acting on behalf of a specific user, generate an Access Token and Access Secret in the same section.
2. Add them to .dlt/secrets.toml
[sources.twitter_source] bearer_token = "your_bearer_token_here" # If using OAuth 1.0a for user-context: # api_key = "your_api_key" # api_secret = "your_api_secret" # access_token = "your_access_token" # access_token_secret = "your_access_token_secret"
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 Twitter 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 twitter_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline twitter_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset twitter_data The duckdb destination used duckdb:/twitter.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 /2/tweets/search/recent and /2/users/
/tweets from the Twitter 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 twitter_source(bearer_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.x.com/2", "auth": {"type": "bearer", "token": bearer_token}, }, "resources": [ {"name": "tweets", "endpoint": {"path": "2/tweets", "data_selector": "data"}}, {"name": "recent_search", "endpoint": {"path": "2/tweets/search/recent", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="twitter_pipeline", destination="duckdb", dataset_name="twitter_data", ) load_info = pipeline.run(twitter_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("twitter_pipeline").dataset() sessions_df = data.recent_search.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM twitter_data.recent_search LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("twitter_pipeline").dataset() data.recent_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 Twitter 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 Twitter?
Request dlt skills, commands, AGENT.md files, and AI-native context.