> For the complete documentation index, see [llms.txt](https://faq.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.blink.sv/integrations/set-your-blink-account-as-an-lnbits-funding-source.md).

# Set your Blink account as an LNbits funding source

Since LNbits v0.12.10 Blink is available to be set as a funding source in the LNbits Server Settings.\
\
Steps to set up:\
\
\* get a Blink API key at [dashboard.blink.sv](https://dashboard.blink.sv\)). Find more details about the Dashboard and API keys [here](https://dev.blink.sv/api/auth).\
\
\* log in as the [LNbits super user](https://github.com/lnbits/lnbits/blob/dev/docs/guide/admin_ui.md)

\* open the `Server` settings

![](https://4187605819-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrDjkhoZ590xyogoMxo5l%2Fuploads%2Fgit-blob-d7273550c99247d444ce9e148461694c8b45d2bb%2Flnbits_super_user.png?alt=media)\\

\* choose `Blink` from the dropdown menu under `Funding Sources` **-** `Active Funding (Requires server restart)`\
\* paste your API key to the `Key` field

\
![](https://4187605819-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrDjkhoZ590xyogoMxo5l%2Fuploads%2Fgit-blob-55d8b66c3509f1e7a3750c641fc6b97a24034db3%2Flnbits_funding_sources.png?alt=media)

\* restart LNbits\
\
\* alternatively can edit the LNbits `.env` file directly as well if have access to the terminal on the server


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://faq.blink.sv/integrations/set-your-blink-account-as-an-lnbits-funding-source.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.