Load Feedlyboard data to DuckDB

Feedly is a REST API that allows users to automate workflows and integrate Feedly's intelligence features into other systems. Everything needed to build a working Feedlyboard → 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 Feedlyboard 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 Feedlyboard 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 Feedlyboard 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.

---

Feedlyboard API at a glance

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

---

How do I authenticate with the Feedlyboard API?

All API requests must be authenticated by including an 'Authorization' header with a Bearer token in the format 'Authorization: Bearer '.

1. Get your credentials

To obtain Feedly API credentials, follow these steps: 1. Navigate to the Feedly self-service API page at https://feedly.com/i/team/api (this requires an Enterprise account or specific API access). 2. If you do not see a table with API tokens, contact sales@feedly.com to request access. 3. On the self-service page, click the 'New API Token' button. 4. Copy the generated token immediately, as it cannot be retrieved again once the dialog is closed. For production integrations requiring public app access, you must create an application in the Feedly Developer Console to obtain a Client ID and Client Secret for OAuth 2.0 flows.

2. Add them to .dlt/secrets.toml

Copy
[sources.feedlyboard_source]
feedly_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 Feedlyboard data can I load into DuckDB?

These are the Feedlyboard endpoints dlt can load into DuckDB:

---

How do I load only new Feedlyboard records?

Feedlyboard exposes continuation on v3/streams/contents, 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": "stream_contents", "endpoint": {
    "path": "v3/streams/contents",
    "data_selector": "items",
    "incremental": {"cursor_path": "continuation", "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 Feedlyboard pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading search and streams (often used as streams/contents) from the Feedlyboard API into DuckDB:

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

@dlt.source
def feedlyboard_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.feedly.com/v3",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "stream_contents", "endpoint": {"path": "v3/streams/contents", "data_selector": "items"}},
            {"name": "search", "endpoint": {"path": "v3/search/contents", "data_selector": "results"}}
        ],
    }
    yield from rest_api_resources(config)


def load_feedlyboard_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="feedlyboard_pipeline",
        destination="duckdb",
        dataset_name="feedlyboard_data",
    )
    load_info = pipeline.run(feedlyboard_source())
    print(load_info)


if __name__ == "__main__":
    load_feedlyboard_to_duckdb()

Run it with python feedlyboard_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 Feedlyboard 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("feedlyboard_pipeline").dataset()
df = data.stream_contents.df()
print(df.head())

SQL:

Copy
SELECT * FROM feedlyboard_data.stream_contents LIMIT 10;

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

---

How do I deploy the Feedlyboard 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 Feedlyboard 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 Feedlyboard 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