Does RIB BuildSmart publish a public API?
No. RIB BuildSmart — the construction accounting product now part of RIB Software (a Schneider Electric company) — does not publish a public API. There is no developer portal or public API documentation on the RIB Software site, and the former ribccs.com domain now redirects to rib-software.com, which has no developer section either.
That is not unusual for hosted construction accounting systems of BuildSmart's generation. It does, however, shape what any third-party tool can honestly claim about "integrating" with it.
What does no public API mean for expense automation?
It means no card or expense platform can sync transactions into BuildSmart the way they do with cloud systems that expose an API. Anyone promising a live, automatic feed into BuildSmart is describing something the software does not publicly support. In practice, card spend reaches BuildSmart one of two ways: someone keys transactions in by hand, or the data arrives as a file BuildSmart can import.
For a construction company, hand-keying is the expensive path. Every card transaction has to be coded to the right job and cost code, matched to a receipt, and entered — usually by the accounts team at month end, from statements and a shoebox of receipts.
How does Vergo work with RIB BuildSmart without an API?
Vergo takes the file route and does the coding work upstream. Cardholders capture receipts and code transactions to jobs and cost codes in Vergo as they spend. Vergo then provides custom-built CSV exports matched to the import format BuildSmart expects, so your finance team imports a clean, coded batch instead of keying entries one at a time.
To be clear about what this is: a structured file import, not an API sync. Nothing posts into BuildSmart automatically. The gain is that everything arriving in the import file is already coded, receipt-backed, and approved — the import step becomes minutes of review rather than days of data entry.
Is a CSV import a real integration?
For a system without a public API, a correctly formatted file import is the working automation path — and file-based workflows are how BuildSmart sites already move data in practice. The difference between a generic CSV dump and a usable one is the mapping: columns, account references, and job and cost-code fields have to line up with what BuildSmart's import expects. That mapping work is what Vergo builds per system, so the export is import-ready rather than a spreadsheet someone still has to rework.
What should a BuildSmart site check before buying a card platform?
Ask any vendor exactly how their data gets into BuildSmart. If the answer implies an API connection, ask for the BuildSmart API documentation it uses — there is none published. The honest answers are manual entry or file import. From there, compare how much coding work the platform does before the file is produced: job and cost-code tagging at the point of spend, receipt matching, and approvals are what determine whether the import lands clean.
Does RIB BuildSmart have a public API?
No. RIB Software publishes no public API or developer documentation for BuildSmart. There is no developer portal on rib-software.com, and the legacy ribccs.com domain redirects there.
Can card transactions sync into BuildSmart automatically?
No platform can post transactions into BuildSmart through a public API, because none exists. Data gets in by manual entry or by importing a correctly formatted file.
How does Vergo connect to RIB BuildSmart?
Vergo provides custom-built CSV exports matched to BuildSmart's import format. Transactions are coded to jobs and cost codes and receipt-matched in Vergo first, so the file imports clean.
Is a file import enough for month-end close?
Yes, when the file is already coded and approved. The import replaces line-by-line data entry; your team reviews a batch instead of keying transactions from statements.
