Talkwalker Python API Docs | dltHub
Build a Talkwalker-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Talkwalker is a social listening and analytics platform providing APIs to search mentions, manage project resources, streaming and modify documents. The REST API base URL is https://api.talkwalker.com and all requests require an access_token query parameter.
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 Talkwalker data in under 10 minutes.
What data can I load from Talkwalker?
Here are some of the endpoints you can load from Talkwalker:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| resources | /api/v2/talkwalker/p/{project_id}/resources | GET | result_resources.projects | List project resources (topics, filters, channels, events, panels, datasets) |
| tags | /api/v2/talkwalker/p/{project_id}/tags | GET | result_tags.tags | List tag IDs defined in a project |
| views | /api/v2/talkwalker/p/{project_id}/views | GET | result_views.projects | List dashboards/reports/alerts in a project |
| topics_list | /api/v2/talkwalker/p/{project_id}/topics/list | GET | (response shows top‑level object with topics) | List topics with definitions for a project |
| search_results | /api/v1/search/results | GET | (varies) | Retrieve documents from global index or project |
How do I authenticate with the Talkwalker API?
The APIs use an access_token passed as a query parameter for project‑scoped read/write calls.
1. Get your credentials
- Log into Talkwalker account dashboard; 2) Create or open an API application / project in the developer/API section; 3) Generate an access token (read or read/write) for that project; 4) Copy the access_token shown and use it in the access_token query parameter for API calls.
2. Add them to .dlt/secrets.toml
[sources.talkwalker_source] access_token = "your_access_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:
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 Talkwalker 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 talkwalker_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline talkwalker_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset talkwalker_data The duckdb destination used duckdb:/talkwalker.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline talkwalker_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 resources and tags from the Talkwalker 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 talkwalker_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.talkwalker.com", "auth": { "type": "api_key", "access_token": access_token, }, }, "resources": [ {"name": "resources", "endpoint": {"path": "api/v2/talkwalker/p/{project_id}/resources", "data_selector": "result_resources.projects"}}, {"name": "tags", "endpoint": {"path": "api/v2/talkwalker/p/{project_id}/tags", "data_selector": "result_tags.tags"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="talkwalker_pipeline", destination="duckdb", dataset_name="talkwalker_data", ) load_info = pipeline.run(talkwalker_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("talkwalker_pipeline").dataset() sessions_df = data.resources.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM talkwalker_data.resources LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("talkwalker_pipeline").dataset() data.resources.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 Talkwalker 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
Ensure you include a valid access_token query parameter (access_token=) obtained from your Talkwalker project. Invalid or missing tokens return a non‑zero status_code and status_message indicating an authentication error.
Rate limits
Resources endpoints are rate‑limited (e.g., resources = 20 calls/min, tags = 40 calls/min). Cache responses and respect per‑endpoint limits.
Pagination & response envelopes
Many endpoints return an envelope object (e.g., result_resources, result_tags, result_views). Drill into the documented key to extract arrays (e.g., result_resources.projects). For the search/results endpoint, confirm at runtime whether documents are in a top‑level array or under a specific key, as examples vary.
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 Talkwalker?
Request dlt skills, commands, AGENT.md files, and AI-native context.