Perigon Python API Docs | dltHub

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

Last updated:

Perigon is an HTTP REST API that provides fast, structured access to global news and events. The REST API base URL is `` and All requests require an API key for authentication..

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 Perigon data in under 10 minutes.


What data can I load from Perigon?

Here are some of the endpoints you can load from Perigon:

ResourceEndpointMethodData selectorDescription
articles/articlesGETarticlesRetrieve news articles matching query parameters.
vector_search/vector-searchGETresultsPerform vector similarity search over article embeddings.
summarizer/summarizerGETsummaryGenerate a summary for a given article.
stories/storiesGETstoriesAccess grouped story clusters.
wikipedia/wikipediaGETentriesSearch Wikipedia entries related to news topics.

How do I authenticate with the Perigon API?

Authentication is performed by sending the API key as a Bearer token in the Authorization header of each request.

1. Get your credentials

  1. Go to https://www.perigon.com and sign up for an account.
  2. After verifying email, log in to the Perigon dashboard.
  3. Navigate to the API Keys or Credentials section.
  4. Click Create New API Key, give it a name, and copy the generated key.
  5. Store the key securely for use in your dlt configuration.

2. Add them to .dlt/secrets.toml

[sources.perigon_data_source] api_key = "your_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 Perigon 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 perigon_data_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline perigon_data_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset perigon_data_data The duckdb destination used duckdb:/perigon_data.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline perigon_data_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 articles and stories from the Perigon 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 perigon_data_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "articles", "endpoint": {"path": "articles", "data_selector": "articles"}}, {"name": "stories", "endpoint": {"path": "stories", "data_selector": "stories"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="perigon_data_pipeline", destination="duckdb", dataset_name="perigon_data_data", ) load_info = pipeline.run(perigon_data_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("perigon_data_pipeline").dataset() sessions_df = data.articles.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM perigon_data_data.articles LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("perigon_data_pipeline").dataset() data.articles.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 Perigon 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.


Troubleshooting

Authentication Errors

  • 401 Unauthorized: Occurs when the API key is missing, malformed, or revoked. Ensure the Authorization: Bearer <api_key> header is present and the key is active.

Rate Limiting

  • 429 Too Many Requests: The API enforces request limits per minute/hour. Back off for the period indicated in the Retry-After header before retrying.

Pagination

  • The API uses page and page_size query parameters. If a response includes a next_page URL, follow it to retrieve subsequent records. Missing or incorrect pagination parameters can result in incomplete data retrieval.

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 Perigon?

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