Load MikroTik data to DuckDB

MikroTik RouterOS REST API provides a JSON-based interface for managing and monitoring RouterOS configuration using standard HTTP methods. Everything needed to build a working MikroTik → 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 MikroTik 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 MikroTik 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 MikroTik 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.

---

MikroTik API at a glance

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

---

How do I authenticate with the MikroTik API?

Authentication is performed via HTTP Basic Auth using the router's console credentials (username and password). The credentials should be provided in the Authorization header.

1. Get your credentials

The MikroTik RouterOS REST API does not use traditional API keys. Instead, it utilizes standard HTTP Basic Authentication. To set up credentials, follow these steps in your MikroTik router (via Winbox, SSH, or WebFig):\n\n1. Create a dedicated API user to follow the principle of least privilege: /user add name=api-user password=strong-password group=read (replace 'read' with specific policies required).\n2. Ensure your user group has the 'api' policy enabled.\n3. Enable the web service in the IP Service menu: /ip service set www-ssl disabled=no port=443 (HTTPS is strongly recommended).\n4. If using HTTPS, assign a valid SSL certificate.\n5. When connecting, provide the created username and password in the HTTP Authorization header.

2. Add them to .dlt/secrets.toml

Copy
[sources.mikrotik_source]
api_key = "REPLACE_ME"

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 MikroTik data can I load into DuckDB?

These are the MikroTik endpoints dlt can load into DuckDB:

---

How do I load only new MikroTik records?

The MikroTik 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": "ip_addresses", "endpoint": {
    "path": "rest/ip/address",
    # 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 MikroTik pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading interface and system/resource (or similar resource-specific paths mapped directly from the RouterOS console menu structure). from the MikroTik API into DuckDB:

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

@dlt.source
def mikrotik_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{router_ip}/rest",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key},
        },
        "resources": [
            {"name": "ip_addresses", "endpoint": {"path": "rest/ip/address"}},
            {"name": "interfaces", "endpoint": {"path": "rest/interface"}}
        ],
    }
    yield from rest_api_resources(config)


def load_mikrotik_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="mikrotik_pipeline",
        destination="duckdb",
        dataset_name="mikrotik_data",
    )
    load_info = pipeline.run(mikrotik_source())
    print(load_info)


if __name__ == "__main__":
    load_mikrotik_to_duckdb()

Run it with python mikrotik_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 MikroTik 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("mikrotik_pipeline").dataset()
df = data.ip_address.df()
print(df.head())

SQL:

Copy
SELECT * FROM mikrotik_data.ip_address LIMIT 10;

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

---

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