[GH-ISSUE #52] API KEY management is a hassle #869

New Issue

GiteaMirror · 2026-04-27T18:03:04-05:00

GiteaMirror commented

2026-04-27 18:03:04 -05:00

Originally created by @xhzeem on GitHub (Nov 13, 2025).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/52

The vault in the system should store the API keys but there is no direct way to know all the keys I need

I suggest to add a tab for every transformer with its API keys empty by default, so it will be way easier to manage the APIs

Tools like subfinder should take tens of different API keys but in the same time I might not want to share them with the other tools + I don't have a list of them with their default key names

Also the mistral API for Flo and other platforms wide apis should have a page so that i know what i need

Originally created by @xhzeem on GitHub (Nov 13, 2025). Original GitHub issue: https://github.com/reconurge/flowsint/issues/52 The vault in the system should store the API keys but there is no direct way to know all the keys I need I suggest to add a tab for every transformer with its API keys empty by default, so it will be way easier to manage the APIs Tools like subfinder should take tens of different API keys but in the same time I might not want to share them with the other tools + I don't have a list of them with their default key names Also the mistral API for Flo and other platforms wide apis should have a page so that i know what i need

GiteaMirror added the documentation enhancement labels 2026-04-27 18:03:05 -05:00

GiteaMirror commented

2026-04-27 18:03:08 -05:00

@dextmorgn commented on GitHub (Nov 13, 2025):

Hey @xhzeem,

You'r right, the API key coverage and documentation is really minimal and quite incomplete.

So you suggestion having the keys tied to the transforms themselves instead of having them global ? I like the idea, as you'd have the same config for the flows as well.

I'll add it to the todo and mark this as important.

@dextmorgn commented on GitHub (Nov 13, 2025): Hey @xhzeem, You'r right, the API key coverage and documentation is really minimal and quite incomplete. So you suggestion having the keys tied to the transforms themselves instead of having them global ? I like the idea, as you'd have the same config for the flows as well. I'll add it to the todo and mark this as important.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/flowsint#869