Core Lightning Python API Docs | dltHub

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

Last updated:

Core Lightning REST API is a REST server that exposes functionalities of a Core Lightning node, allowing interaction with the node via HTTP requests. The REST API base URL is https://127.0.0.1:3010/ and Authentication requires either a rune for CLNRest or a macaroon for c-lightning-REST, passed in the HTTP header..

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


What data can I load from Core Lightning?

Here are some of the endpoints you can load from Core Lightning:

ResourceEndpointMethodData selectorDescription
get_info/v1/getinfoGETGet node information
list_funds/v1/listFundsGEToutputs, channelsReturns on-chain funds and channel funds information
list_peers/v1/peer/listPeersGETpeersReturns the list of peers connected with the node
list_channels/v1/channel/listChannelsGETchannelsGet the list of channels that are known to the node.
list_pays/v1/pay/listPaysGETpaysList result of payment {bolt11}, or all
list_invoices/v1/invoice/listInvoicesGETinvoicesLists the invoice on the node, for a {label} or all.
get_balance/v1/getBalanceGETGet the total balance of the node
get_fees/v1/getFeesGETGet the current fees of the node
decode_utility/v1/utility/decodeGETDecode a bolt11 or bolt12 invoice
list_configs_utility/v1/utility/listConfigsGETList all configurations
new_address/v1/newaddrGETGet a new address for receiving funds
local_remote_balance/v1/channel/localremotebalGETGet local and remote balance of channels
list_payments/v1/pay/listPaymentsGETpaymentsList all payments
list_node_network/v1/network/listNodeGETnodesList all nodes in the network
list_channel_network/v1/network/listChannelGETchannelsList all channels in the network
fee_rates_network/v1/network/feeRatesGETGet fee rates
list_offers/v1/offers/listOffersGEToffersList all offers

How do I authenticate with the Core Lightning API?

For CLNRest, a rune token is required in the rune HTTP header. For c-lightning-REST, a macaroon token (base64 or hex encoded) is required in the macaroon HTTP header.

1. Get your credentials

For CLNRest, a new rune can be created using the createrune command. For c-lightning-REST, the access.macaroon file needs to be read, converted to base64 or hex, and used as the macaroon token.

2. Add them to .dlt/secrets.toml

[sources.core_lightning_source] auth_token = "your_rune_or_macaroon_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 Core Lightning 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 core_lightning_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline core_lightning_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 getinfo and listfunds from the Core Lightning 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 core_lightning_source(auth_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://127.0.0.1:3010/", "auth": { "type": "bearer", "rune or macaroon": auth_token, }, }, "resources": [ {"name": "getinfo", "endpoint": {"path": "v1/getinfo"}}, {"name": "list_funds", "endpoint": {"path": "v1/listFunds", "data_selector": "outputs, channels"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="core_lightning_pipeline", destination="duckdb", dataset_name="core_lightning_data", ) load_info = pipeline.run(core_lightning_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("core_lightning_pipeline").dataset() sessions_df = data.getinfo.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM core_lightning_data.getinfo LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("core_lightning_pipeline").dataset() data.getinfo.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 Core Lightning 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 Failures

Authentication failures typically occur due to incorrect or missing rune (for CLNRest) or macaroon (for c-lightning-REST) in the HTTP headers. Ensure that the token is correctly generated and included in the rune or macaroon header, respectively. For CLNRest, verify the rune has the necessary permissions for the requested operation (e.g., readonly for websocket connections). For c-lightning-REST, ensure the macaroon is base64 or hex encoded as required.

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 Core Lightning?

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