Does Nomi have an API?

Does Nomi publish a public API?

Nomi's own site publishes no public API documentation. There is no developer page, no API reference, and no published toolkit that third-party platforms can build a supported integration against. Mentions of Nomi connectivity elsewhere on the web come from third parties, not from Nomi's own documentation — and for integration purposes, an undocumented API is not a usable one. The honest answer for anyone evaluating expense automation: there is no supported programmatic path into Nomi today.

What does that mean for expense automation?

It means no expense or card platform can truthfully claim a live API sync into Nomi. Card spend has to reach the ledger another way: keyed in by hand, or imported as a file in the structure Nomi accepts. For firms and businesses running their books on Nomi, the recurring cost is the preparation — downloading card statements, reshaping them in a spreadsheet, assigning categories line by line, and chasing receipts to match. That work repeats every period regardless of how modern the accounting platform itself is.

How does Vergo work with Nomi without an API?

Vergo automates everything up to the import step. Vergo issues the corporate cards, so each transaction is captured at the point of spend — receipt attached, category coded, cardholder identified — rather than reconstructed from a statement weeks later. Vergo then generates a custom-built CSV export matched to the import format Nomi expects, so the file loads through Nomi's own import routine without manual reshaping.

The period-end cycle becomes: spend on Vergo cards, coding as it happens, export a matched file, import into Nomi. No retyping, no column-mapping, no receipt chase.

Is a CSV workflow good enough compared to an API sync?

A matched CSV export delivers the outcome that matters — coded transactions in the ledger without manual work — through the channel Nomi actually supports. The difference from a generic export is the matching: a raw statement download still needs a spreadsheet session before Nomi will take it, while a file built against Nomi's import structure is finished the moment it is generated. You also review the file before it loads, so nothing posts to the books unseen.

Should Nomi publish API documentation in future, a deeper connection becomes possible. Until then, the matched export is the working automation path — and it removes the part of the job that was ever manual to begin with. The test worth applying to any integration claim: ask for Nomi's API documentation. If none can be shown, the connection is file-based regardless of the label, and the real question is how much of the file preparation is automated for you.