Does BRIX have an API?

Does BRIX have a public API?

No. BRIX, the construction accounting system acquired by Hyphen Solutions in 2017, does not publish a public API. There is no developer portal, no documented endpoints, and no self-serve way for a third-party application to read from or write to a BRIX company file.

Hyphen Solutions does offer AIM, but AIM is a licensed connector that moves data between BuildPro and an ERP — it is not a BRIX API that outside software can build against.

What does no API mean for expense automation?

Most modern spend platforms assume an API sync: the card platform posts transactions straight into the accounting system. With BRIX, that model is off the table. Any tool that claims a live, automatic sync into BRIX is claiming something the system does not expose.

In practice, a BRIX shop handling company card spend has two options: key transactions in by hand, or move them in through file imports. Manual entry means a bookkeeper re-typing each charge with its job and cost coding — slow, and the usual source of month-end coding errors. File import is the workable automation path, provided the file matches what BRIX expects.

How does Vergo work with BRIX without an API?

Vergo provides custom-built CSV exports matched to BRIX's import format. Card transactions are captured and coded in Vergo — job, cost code, GL account, receipt attached — and then exported as a file structured the way BRIX's import expects, so it loads without column remapping or cleanup.

The flow is straightforward: your team spends on Vergo cards, coding happens in Vergo (from the field or the office), and on whatever cadence you close — weekly, or at month end — you export the file and import it into your hosted BRIX environment. No transaction gets re-keyed.

Is a CSV import worse than an API sync?

It is less automatic, and it is honest to say so: someone runs an export and an import rather than nothing happening at all. But the part that actually costs time — coding each transaction to the right job and cost code, and chasing receipts — is handled in Vergo either way. The import itself takes minutes. For a system like BRIX that publishes no API, a matched file import is the reliable path, not a compromise workaround stacked on fragile screen-scraping.

Could BRIX release an API later?

Hyphen Solutions has not published developer documentation for BRIX, and we do not speculate on roadmaps. If that changes, an API connection would become possible; today, matched CSV import is the supported path.