Does Causeway publish a public API?
No. Causeway does not publish a public API for third-party software to read from or write into its financials. There is no open developer portal or documented endpoint set an expense platform could build against, which means no card or spend tool can push transactions directly into Causeway — whatever a sales page might imply.
What does that mean for a construction finance team?
Construction spend is coding-heavy: a fuel receipt or merchant purchase isn't booked until it carries the right contract or job reference and cost heading. Without an API, that coded data cannot flow into Causeway automatically. The routes that remain are the ones Causeway itself controls — manual entry, or importing structured transaction files into the system.
For a contractor with dozens of cardholders across sites, manual entry means the accounts team retyping statements and chasing paperwork; a raw card statement import means reshaping the provider's file and adding the costing references by hand each month.
How does Vergo work with Causeway without an API?
Vergo moves the coding to the point of spend and delivers the result as a file Causeway can take in. Site and office staff spend on Vergo cards; each transaction is captured with its receipt and coded to the job and cost heading your team uses. When it's time to update Causeway, Vergo generates a custom-built CSV export matched to the import format Causeway expects — download, import, reconcile.
This is a file-based integration, stated plainly: no API sync exists, and Vergo does not pretend one does. What the matched export removes is the reshaping and rekeying between the card and the costing ledger.
Is a direct Causeway connection ever likely?
If Causeway publishes a public API in future, a direct connection would be worth building. Until then, decisions should rest on what exists today, and today the working automation path is a clean, matched file import.
What should a contractor's finance team verify before buying?
Two checks cut through vendor claims. First, ask any platform promising a Causeway sync to point at the public API documentation it built against — there is none to point at. Second, ask to see the import file against your own contract and cost-heading structure, because a file that ignores your costing conventions is a statement, not an integration. Vergo passes the second test by design: the export is matched to Causeway's import format and carries the job coding your team applied at the point of spend.
Can any card platform sync automatically with Causeway?
No. Causeway publishes no public API, so there is no interface for a card or expense platform to sync through. File import is the working path.
How does Vergo handle job costing for Causeway?
Cardholders and approvers code each transaction in Vergo to the job and cost heading it belongs to. Those references travel in the CSV export, so spend arrives in Causeway already costed.
What file does Vergo produce?
A custom-built CSV matched to the import format Causeway expects, containing the period's approved card transactions with dates, merchants, amounts, and coding.
Where do receipts live?
In Vergo, attached to each transaction — captured by the cardholder at the point of purchase and available whenever a cost needs evidencing.
