Does BusinessCraft have a public API?
No. BusinessCraft, the Australian ERP used by builders and construction firms, does not publish a public API. There is no read or write access for third-party software and no developer documentation to build against — this holds for both its cloud and on-premise deployments.
What does no API mean for expense automation?
Spend platforms that promise an ERP sync are describing an API connection, and with BusinessCraft there is none to make. A builder running company cards alongside BusinessCraft gets transactions into the system one of two ways: the accounts team keys them in with job and cost-centre coding, or they arrive by file import.
Keying them in is the slow path — every charge typed with its coding, receipts reconciled separately, all of it stacked onto the close.
How does Vergo work with BusinessCraft without an API?
Vergo provides custom-built CSV exports matched to BusinessCraft's import format. Card spend is captured and coded in Vergo — job, cost centre, account, with the receipt attached at purchase — and exported as a file shaped for BusinessCraft's import. Your accounts team loads it on whatever cadence you close, and no transaction is typed twice.
Does deployment — cloud or on-premise — change this?
No. Neither deployment exposes a public API, so the file-import path is the same in both: the export comes from Vergo, the import runs in your BusinessCraft environment wherever it lives.
Is a matched CSV import a real integration?
It is the integration BusinessCraft supports, and we say so plainly rather than implying a sync the system cannot do. The costly work — coding each charge to the right job and collecting receipts — happens in Vergo regardless; the import itself takes minutes.
What should a builder ask a card vendor about BusinessCraft?
One question settles it: how, exactly, do transactions get from your platform into BusinessCraft? An answer that implies a live sync is describing an API the system does not expose. The credible answer names a file matched to BusinessCraft's import layout and explains where the job and cost-centre coding on each line comes from. Vergo's answer is specific: coding happens in Vergo at the point of purchase, and the export is built to the layout your import already accepts.
Could BusinessCraft release an API?
The vendor has published no developer documentation, and we do not speculate on roadmaps. Today, the matched CSV export is the working automation path.
Does BusinessCraft publish an API?
No. BusinessCraft exposes no public API — no read or write access and no developer documentation — in either its cloud or on-premise form.
How does Vergo integrate with BusinessCraft?
Through custom-built CSV exports matched to BusinessCraft's import format. Coded card transactions are exported from Vergo and imported into BusinessCraft.
Can card spend carry job coding into BusinessCraft?
Yes. Each transaction is coded to its job and cost centre in Vergo before export, so imported entries arrive fully coded.
Does it matter if we run BusinessCraft on-premise?
No. The import workflow is identical for cloud and on-premise — the file comes from Vergo and loads into your environment either way.
