Does Capium publish a public API?
No. Capium, the UK cloud suite for accountancy practices, does not publish a public API for third-party software. This is not a gap in the documentation — Capium's own support material explicitly states that no public API is available. There is no developer portal, no published endpoints, and no way for an outside application to read from or post into a Capium client's books programmatically.
Capium does offer bank feeds inside the product, but those run over open-banking connections between banks and Capium — they are not a software-to-software interface that an expense platform can plug into.
What does no API mean for expense automation?
It means any tool promising a live, automatic sync into Capium is overstating what is possible today. Without an API, an expense or corporate-card platform cannot push transactions, receipts, or coding directly into a client's ledger. The realistic paths are the ones Capium itself supports: its built-in bank feeds for bank accounts, and file import for everything else.
For a practice managing card spend across clients, that usually leaves manual entry or a spreadsheet shuffle — exporting from the card provider, reshaping columns, and importing client by client.
How does Vergo work with Capium without an API?
Vergo takes the file-import path and does the reshaping for you. Card transactions captured in Vergo — already coded with receipts attached — are exported as custom-built CSV files matched to the import format Capium expects. Instead of massaging a generic card statement into the right columns, you download a file that is ready to import as-is.
To be clear about what this is and is not: it is not an API sync, and Vergo does not claim one exists. It is a repeatable file-based workflow — the honest automation path for a system with no public API. Because Capium is cloud-hosted, the import itself happens in the browser, and the routine is the same from any machine.
Could Capium add a public API later?
Possibly — cloud accounting vendors do open up over time. But as of today the vendor's position is explicit, and any integration decision should be based on what exists now: file import in, reports out. If that changes, a direct connection would become worth revisiting; until then, matched CSV exports are the working path.
What should a practice check before choosing an expense tool for Capium?
Ask two questions of any vendor. First: show me the connection — if the claim is a live sync, ask where Capium's public API documentation is, because none exists. Second: show me the file — a matched export you can test against a real client's books in minutes. A tool that answers the second question honestly, as Vergo does, saves the practice from discovering the difference between a demo promise and a month-end reality. The bookkeeping team keeps its existing Capium import routine; the file feeding it simply gets clean and consistent.
Is there a Capium developer portal or API documentation?
No. Capium publishes no developer documentation, and its support material explicitly states that a public API is not available to third-party software.
Do Capium's bank feeds count as an API?
Not for integration purposes. The bank feeds connect banks to Capium over open banking; they are not an interface other software can use to read or write ledger data.
How does Vergo get card transactions into Capium?
Vergo produces custom-built CSV exports matched to Capium's import format. Transactions coded in Vergo download as a file ready to import into Capium — no column remapping, no rekeying.
Is a CSV workflow reliable enough for a practice?
Yes, provided the file matches the expected format every time — which is exactly what the matched export is for. The routine is the same each period: export from Vergo, import into Capium, reconcile.
