Import API as a Custom Source

I would like to propose adding an Import API that allows users (or external tools) to push transactions into Lunch Flow as a source, instead of Lunch Flow having to connect to the bank directly.

This would also pair incredibly well with the middleware suggestion. Providing more modular processing pieces to user self imported data.


Why this is useful

Some users have:

• banks with no PSD2/aggregation support

• internal systems (business bookkeeping, custom exports)

• bank APIs that only allow personal access tokens

• scripts that already fetch transactions from their bank
  

Currently, these users would have to write both:

1. their own source integration, and

2. logic for pushing the data into their destination (Actual, YNAB, etc.)

An Import API would remove the need to write destination logic.

The user sends raw transactions to Lunch Flow once, and Lunch Flow handles the formatting and destination sync. This lowers the barrier for supporting “rare” banks and edge-case integrations.


Requirements / Expectations

1. Simple authenticated endpoint

2. Accepts standardized transaction payload

3. Lunch Flow handles the rest
   After posting the transaction, Lunch Flow would:

   • apply any configured middleware (if middleware is implemented)

   • send the final processed transaction to the destination(s)

Example Use Cases

• Someone has access to a bank API that isn’t supported by aggregation providers.

• A script exports CSV data periodically, instead of writing parsing + categorizing + destination logic, the script simply posts the raw transactions.

• Users with multiple systems (business + personal accounts) that want a unified flow through Lunch Flow