Load Fio data to DuckDB

Fio (FNAR) is a JSON-based REST API for submitting and retrieving environmental and game-related data. Everything needed to build a working Fio → 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 Fio 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 Fio 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 Fio 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.

---

Fio API at a glance

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

---

How do I authenticate with the Fio API?

Authentication is performed by embedding the API key or token directly within the URL path or as a query parameter, depending on the specific service. No separate headers are required.

1. Get your credentials

1. Log in to your Fio banka Internetbanking account.\n2. Navigate to 'Settings' (the gear icon or button in the upper right corner).\n3. Go to the 'API' tab.\n4. Click to create a new token. Note that the request may require strong authorization (e.g., SMS, push notification) depending on your account settings.\n5. If multiple signatures are required for your account, the token must be co-signed by all authorized parties.\n6. Once authorized, the 64-character token will appear in the API overview. It becomes active for use in API requests 5 minutes after successful authorization.

2. Add them to .dlt/secrets.toml

Copy
[sources.fio_source]
api_token = "your_64_character_api_token_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 Fio data can I load into DuckDB?

These are the Fio endpoints dlt can load into DuckDB:

---

How do I load only new Fio records?

The Fio 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.

Copy
{"name": "transactions_by_period", "endpoint": {
    "path": "rest/periods/{token}/{date_from}/{date_to}/transactions.json",
    # 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 Fio pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading movements_in_period and statements from the Fio API into DuckDB:

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

@dlt.source
def fio_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://rest.fnar.net",
            "auth": {"type": "api_key", "api_key": api_key},
        },
        "resources": [
            {"name": "transactions_by_period", "endpoint": {"path": "rest/periods/{token}/{date_from}/{date_to}/transactions.json", "data_selector": "accountStatement.transactionList.transactionInfo"}},
            {"name": "transactions_last", "endpoint": {"path": "rest/last/{token}/transactions.json", "data_selector": "accountStatement.transactionList.transactionInfo"}}
        ],
    }
    yield from rest_api_resources(config)


def load_fio_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="fio_pipeline",
        destination="duckdb",
        dataset_name="fio_data",
    )
    load_info = pipeline.run(fio_source())
    print(load_info)


if __name__ == "__main__":
    load_fio_to_duckdb()

Run it with python fio_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 Fio 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("fio_pipeline").dataset()
df = data.transactions_last.df()
print(df.head())

SQL:

Copy
SELECT * FROM fio_data.transactions_last LIMIT 10;

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

---

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