Load API Changelog data to DuckDB

Changelog is a developer-focused media company and podcast network whose open-source platform manages podcast metadata, show notes, and CMS content. Everything needed to build a working API Changelog → 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 API Changelog to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from API Changelog 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 API Changelog 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.

---

API Changelog API at a glance

These values come from the API Changelog API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the API Changelog API?

The Changelog platform is an open-source Elixir/Phoenix application that does not provide a public REST API for external use; it relies primarily on GitHub OAuth for internal authentication.

No credentials required. The API Changelog API is public, so there is nothing to obtain and nothing to add to .dlt/secrets.toml — the pipeline above runs as written.

---

What API Changelog data can I load into DuckDB?

These are the API Changelog endpoints dlt can load into DuckDB:

---

How do I load only new API Changelog records?

API Changelog exposes updated_at on catalog/changes, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "catalog_changes", "endpoint": {
    "path": "catalog/changes",
    "data_selector": "products",
    "incremental": {"cursor_path": "updated_at", "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 API Changelog pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading p/{post-slug} and sitemap/2026 from the API Changelog API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def api_changelog_source():
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://changelog.com",
        },
        "resources": [
            {"name": "catalog_changes", "endpoint": {"path": "catalog/changes", "data_selector": "products"}},
            {"name": "tickets", "endpoint": {"path": "incremental/tickets", "data_selector": "tickets"}}
        ],
    }
    yield from rest_api_resources(config)


def load_api_changelog_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="api_changelog_pipeline",
        destination="duckdb",
        dataset_name="api_changelog_data",
    )
    load_info = pipeline.run(api_changelog_source())
    print(load_info)


if __name__ == "__main__":
    load_api_changelog_to_duckdb()

Run it with python api_changelog_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 API Changelog 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):

Copy
import dlt

data = dlt.pipeline("api_changelog_pipeline").dataset()
df = data.catalog_changes.df()
print(df.head())

SQL:

Copy
SELECT * FROM api_changelog_data.catalog_changes LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the API Changelog 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 API Changelog loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load API Changelog data to?

dlt loads into any of these — only the destination argument changes:

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

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack