Import and filter transaction data directly from N26 account into lunch money. (100% experimental at the moment but security is my number one priority)
-d int
Search for the last n days for any transactions (if not in webserver mode) (default 1)
-webserver
Run the application as a webserver
The application is meant to be run in one of two ways.
- Execute a binary on your local computer that retrieves transactions from N26 and inserts them into LunchMoney with some terminal output. (standalone mode)
- With the browser extension installed on any (desktop) device and the application running as a webserver on a trusted machine you can execute this flow from anywhere and get some nice UI. (webserver mode)
When running the application 'locally' both flags are required to be set. When running the application as a web server only the webserver flag needs to be set.
- To query the last
ndays for transactions not in webserver mode:./lunchMoneyN26 -d n
When running the application in webserver mode requests must be in the following form:
POST http://[server's ip]:2944/transcations?days=n where you want to search for transactions within the last n days. Starting the application in webserver mode only requires the webserver flag to be set.
- To start the application in web server mode:
./lunchMoneyN26 -webserver
All of the following variables must be set in a .env file placed at the root of the project
| Variable | Description |
|---|---|
N26_USERNAME |
The email associated with your N26 account |
N26_PASSWORD |
Your password associated with your N26 account |
N26_DEVICE_TOKEN |
A random UUIDV4. Can easily be generated here |
LUNCHMONEY_TOKEN |
API token to access your lunch money account which can be retrieved here |
API_PORT |
API port to be used when in webserver mode |
- How can I trust this if I have to give it my login details for N26?
When using this project in either as a webserver or locally your login credentials only need to be persisted through a .env file thats saved locally. The Guitmz/n26 package (outside of ensuring they're set) is the only piece of code that accesses them when it interacts with N26. I've gone through every line of that codebase myself and you should too. I'm not planning on updating many dependencies without checking all changes again. Please also read all of the code in this project while you're at it. The backend is quite simple (just uses gorilla mux for hosting a webserver) on purpose.