Importing configuration file for providers

[karneaud]

is there no way to provide a configuration file list of providers( custom or otherwise) and ${PROVIDER}_API_KEY ?

[diegosouzapw]

@karneaud I don't know of a single "providers config file" import in OmniRoute, and I couldn't find a ${PROVIDER}_API_KEY environment variable convention for adding providers either (I searched the environment reference for v3.8.52; I may have missed something). What exists, as I know it: providers and their keys are stored as connections in the database, added in the dashboard (the bulk-add flow takes one key per line) or through the dashboard's API routes; the full settings/database can be exported and imported from the backup/restore feature.

To point you to the right thing: are you trying to set up a fresh OmniRoute automatically (Docker/CI), move your providers from another instance, or keep keys out of the dashboard? If the last two, tell us which and I'll check what the closest supported route is. If it's an automatic setup you'd like as a feature, it's worth opening a feature request with an example of the file you'd expect.

[karneaud]

looking at migrating to omniroute but i have a list of keys with the env conventions and a .json configuration file. Thought i could have at least import or re-use the resources I already had. I'll look into something else

[mrx-arafat]

Adding to @diegosouzapw's reply: there's also Dashboard → Providers → Import from file, which takes a CSV or JSON list with a different provider per entry. The file format uses provider, name, apiKey, and optional baseUrl and priority. The key goes in apiKey as-is, since ${PROVIDER}_API_KEY references aren't expanded.

For a custom OpenAI/Anthropic-compatible endpoint, create the node in Providers first and use its ID as provider, because the import doesn't create nodes. Diego can correct me if that's changed.

[diegosouzapw]

@mrx-arafat Thank you, and @karneaud: I need to correct my earlier answer. I said I didn't know of a way to import providers from a file, and that was wrong; I missed it. There is: Dashboard → Providers → Import from file (documented in docs/providers/CSV-IMPORT.md, present in v3.8.52). It takes a CSV or JSON list where each row can be a different provider, with provider, name, apiKey and optional baseUrl and priority; a "Download CSV template" button is in the modal, and valid rows import even if others fail. As noted above, the key goes in apiKey as-is (a ${PROVIDER}_API_KEY reference isn't expanded), and custom OpenAI/Anthropic-compatible endpoints must be created as nodes first.

So you may be able to reuse your key list after converting it to that format, even though your env-style .json won't import directly.