Does Xpedeon have a public API?
No. Xpedeon, the hosted construction ERP, does not publish a public API. There is no developer documentation to build against and no endpoint an expense platform can use to post transactions directly into the system. Any vendor claiming a live API sync with Xpedeon is claiming something Xpedeon has not made available.
What does no API mean for expense automation?
It means the last step of card-expense automation — landing finished entries in Xpedeon — has to happen by file import rather than direct sync. Everything upstream of that step still automates fully: issuing cards with controls, capturing receipts at the point of spend, and coding each transaction against the right job before it ever reaches finance. The import is the one step that stays file-based, because that is the interface Xpedeon offers.
For construction finance teams this matters most at month end. Card spend that arrives uncoded — a statement export with no job, no cost allocation, no receipts — has to be reconstructed line by line before it can go anywhere near job costing. The bottleneck is not the import mechanism; it is the missing data.
How does Vergo work with Xpedeon without an API?
Vergo integrates with Xpedeon by producing structured CSV exports custom-built to match the import format Xpedeon expects. Cardholders code spend as it happens — job, cost allocation, receipt attached — from the field. Finance reviews the coded transactions in Vergo, then exports a file shaped for Xpedeon's import rather than a generic bank CSV that needs remapping.
Because Xpedeon is hosted, the import runs in your Xpedeon environment like any other data load: bring the file in through the import routine, and the period's card spend lands as coded entries. Vergo does not claim an API connection to Xpedeon, because none is published — the matched-format export is the honest automation path, and it removes the same manual work a sync would.
Could Xpedeon publish an API later?
Vendors do open up over time, and if Xpedeon publishes a public API the integration can deepen. Until that documentation exists, the working path is the file — and a file that arrives pre-coded to jobs, in the layout Xpedeon ingests, is a short import step rather than a month-end project.
Does Xpedeon have a public API?
No. Xpedeon does not publish a public API, so no expense or card platform can build a direct sync into it. Integrations with Xpedeon are file-based.
How does Vergo integrate with Xpedeon?
Vergo generates custom-built CSV exports matched to the import format Xpedeon expects. Card transactions are coded to jobs in Vergo, exported, and imported into Xpedeon as structured entries.
Can card transactions carry job costing into Xpedeon?
Yes — coding happens in Vergo at the point of spend, so each line in the export already carries its job and cost allocation when Xpedeon ingests the file.
Is a file import slower than an API sync?
The import itself takes minutes at whatever cadence you choose. The real time cost in card expenses is uncoded transactions and missing receipts, and those are eliminated before export.
