Does Inn-Flow offer a public API?
No. Inn-Flow, the hosted hotel accounting platform, does not publish a public API. Its integrations page lists named partners, but nowhere does it document an open API that outside software — or a hotel group's own developers — can build against. Connections into Inn-Flow are partnerships Inn-Flow itself builds, not something a third-party product can set up on its own.
What does that mean for expense automation at a hotel group?
It means no card or expense platform can offer a genuine API sync into Inn-Flow. If a platform is not one of Inn-Flow's named partners, its "integration" is a file — and the useful question is whether that file matches what Inn-Flow's import expects, or whether your accounting team spends the first days of each month reshaping card exports property by property. For a group running several properties, that spreadsheet work multiplies fast.
How does Vergo work with Inn-Flow without an API?
Vergo makes the file itself do the job, and builds it properly. Card transactions are captured the moment they settle and coded in Vergo with the structure your Inn-Flow setup uses — property, department, GL account. Vergo then generates a custom-built CSV export matched to the import format your Inn-Flow system expects. Your accounting team loads it as a normal import: one clean, coded batch instead of a month of statement lines. Because Inn-Flow is hosted, there is nothing to install on your side either — the workflow is cards and receipts in Vergo, one export, one import.
Is a file-based workflow enough for hotel card spend?
Yes — because the file transfer was never the bottleneck. What eats time in hotel expense management is chasing receipts from department heads and GMs across properties and coding hundreds of small card purchases. Vergo automates that at the point of spend: receipts captured by phone, coding applied by rules. By month-end the batch is already clean, and the Inn-Flow import takes minutes. Your controller also keeps a review step before anything posts — a batch that is read before it is loaded is easier to trust than an invisible background sync, especially when spend spans several properties and dozens of cardholders with different levels of accounting discipline.
What if Inn-Flow publishes an API in future?
Then the last step changes and nothing else does. Cards, receipt capture, and coding all live in Vergo either way; the export would simply be replaced by a direct connection. Until Inn-Flow documents a public API, we will not claim one.
Does Inn-Flow have a public API?
No. Inn-Flow does not publish a public API. Its integrations page names partner products, but there is no open developer documentation for third-party software to connect through.
How does Vergo integrate with Inn-Flow?
Through custom-built CSV exports matched to the import format Inn-Flow expects. Card transactions are coded in Vergo — property, department, GL account — and exported as a file your team imports into Inn-Flow as a standard batch.
Does this work across multiple properties?
Yes. Transactions are coded to the right property and department in Vergo during the month, so the export reflects your multi-property structure rather than one flat statement that has to be split by hand.
Can any card platform sync to Inn-Flow in real time?
Not through a public API, because Inn-Flow does not publish one. Unless a platform is a named Inn-Flow partner, its working path is file import — and Vergo builds its files specifically to match Inn-Flow's format.
