Load GNews data to DuckDB
Build a GNews to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the GNews API base URL, auth, endpoints, and incremental loading.
GNews is a REST API service for searching and retrieving real-time and historical news articles from worldwide sources. Everything needed to build a working GNews → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.
Build your GNews to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from GNews to DuckDB and run it on dltHub
That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the GNews API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →
Prefer to write it yourself? Every fact the agent uses is below.
GNews API at a glance
| Base URL | https://gnews.io/api/v4 |
| Example endpoint | GET api/v4/search |
| Records found at | articles |
| Authentication | all requests require an API key passed either as a query parameter or an HTTP header — sent in the X-Api-Key header |
| Pagination | Page-number page size via max |
| API reference | https://docs.gnews.io/authentication |
These values come from the GNews API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the GNews API?
Authentication is performed using an API key which can be provided either as a query parameter named 'apikey' or via the 'X-Api-Key' HTTP header.
1. Get your credentials
To obtain your GNews API credentials, first sign up for a free account at https://gnews.io/register. Once registered and logged in, navigate to your account dashboard. Your API key will be displayed there immediately and is ready for use in your API requests.
2. Add them to .dlt/secrets.toml
[sources.gnews_source] gnews_source_api_key = "your_api_key_here"
dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.
What GNews data can I load into DuckDB?
These are the GNews endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| search | search | GET | articles | Search news articles by keywords. |
| top_headlines | top-headlines | GET | articles | Get top news headlines by category. |
How do I load only new GNews records?
The GNews API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.
{"name": "search", "endpoint": { "path": "api/v4/search", # Replace with a field that increases on every write. "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"}, }}
On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.
What does the generated GNews pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading search and top-headlines from the GNews API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def gnews_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://gnews.io/api/v4", "auth": {"type": "api_key", "api_key": api_key, "name": "X-Api-Key", "location": "header"}, }, "resources": [ {"name": "search", "endpoint": {"path": "api/v4/search", "data_selector": "articles"}}, {"name": "top_headlines", "endpoint": {"path": "api/v4/top-headlines", "data_selector": "articles"}} ], } yield from rest_api_resources(config) def load_gnews_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="gnews_pipeline", destination="duckdb", dataset_name="gnews_data", ) load_info = pipeline.run(gnews_source()) print(load_info) if __name__ == "__main__": load_gnews_to_duckdb()
Run it with python gnews_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.
How do I query GNews data in DuckDB?
dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("gnews_pipeline").dataset() df = data.search.df() print(df.head())
SQL:
SELECT * FROM gnews_data.search LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the GNews to DuckDB pipeline in production?
The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.
- Deploy & schedule — run the pipeline as a managed job with automatic retries.
- Monitor — observable job queues, alerting, and load metrics for every run.
- Transform — promote raw GNews loads into governed, documented models.
- Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.
What other destinations can I load GNews data to?
dlt loads into any of these — only the destination argument changes:
| Destination | Example value |
|---|---|
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.
Next steps
Was this page helpful?
Community Hub
Need more dlt context for GNews to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.