Does Databuild publish a public API?
No. Databuild does not publish public API documentation. Its partner page lists genuine integrations — payroll via KeyPay and field connectivity via OnSite Companion among them — but a partner list is not a developer platform: Databuild publishes nothing programmatic that an outside application could build against. There are no documented endpoints, no authentication guide, and no open interface.
What do the existing partner integrations tell us?
They tell us Databuild can exchange data with specific products under specific arrangements. The KeyPay payroll link, for instance, is a real, documented integration. But each of these is a bespoke connection between two vendors, not evidence of an API any expense platform could use. For everything outside that named list, the way into Databuild is its import capability.
What does no public API mean for expense automation?
It means no card program can claim a live sync into Databuild. The automation has to happen before the data reaches Databuild: capturing receipts, coding spend to jobs and cost centres, and shaping the result into a file Databuild imports cleanly. Done properly, that delivers the same end state as an API — coded card transactions in Databuild without manual entry.
How does Vergo work with Databuild?
Vergo provides custom-built CSV exports matched to Databuild's import format. Site staff and office cardholders spend on Vergo cards, attach receipts, and code purchases to the right job as they happen. Vergo then generates a structured export shaped for your Databuild setup, and your bookkeeper brings it in as one file. Cost reporting in Databuild stays current because the coding was done at the point of purchase, not reconstructed at month end.
Should you wait for Databuild to publish an API?
There is no published indication one is coming, and builders need job costs current now. The CSV path is documented, working, and does not depend on Databuild's roadmap.
Does Databuild have a public API for developers?
No. Databuild's partner page lists specific integrations like KeyPay, but Databuild publishes nothing programmatic — no public API documentation exists.
How does Vergo integrate with Databuild?
Through custom-built CSV exports matched to Databuild's import format. Job-coded card transactions leave Vergo as one structured file for import into Databuild.
Doesn't the KeyPay integration prove Databuild has an API?
No — KeyPay is a bespoke vendor-to-vendor integration. It shows Databuild can exchange data with named partners, not that an open API exists for other tools.
Can card spend be coded to jobs before it reaches Databuild?
Yes. Cardholders code purchases to jobs in Vergo at the time of spend, so the imported file already carries job coding for Databuild's cost reporting.
