Does Builder Information System have a public API?
No. Builder Information System (BIS) is a desktop construction accounting package, and it publishes no public API — no read access, no write access, no developer portal or documented endpoints for third-party software.
As a desktop product, BIS holds its data locally, which makes an API connection even less likely than with hosted systems: there is no cloud endpoint for outside software to reach even in principle.
What does no API mean for expense automation?
Card platforms that advertise an accounting sync depend on an API, and BIS does not expose one. A contractor running company cards alongside BIS therefore lands in one of two workflows: the bookkeeper keys card charges into BIS by hand, with job and cost coding, or transactions come in through a file import.
Manual entry is where the month-end hours go — and where coding to the wrong job happens, which is what distorts job cost reports.
How does Vergo work with BIS without an API?
Vergo provides custom-built CSV exports matched to Builder Information System's import format. Card spend is captured and coded in Vergo — job, cost code, GL account, receipt attached at the point of purchase — and exported as a file shaped for BIS's import. Your bookkeeper loads it into BIS on your close cadence; nothing is typed twice.
Is file import good enough for job costing?
Yes — because the job costing happens before the file exists. Each transaction is coded to its job and cost code in Vergo, often by the person who made the purchase, so the file that reaches BIS carries complete coding. Your BIS job cost reports pick up card spend with the same detail as any other entry.
What should a contractor ask a card vendor about BIS?
Ask how, specifically, transactions get from the card platform into Builder Information System. If the answer implies a live sync, it is describing an API that BIS does not expose. The credible answer names a file matched to BIS's import layout and explains where the job and cost-code coding comes from. Vergo's answer is concrete: coding happens in Vergo at the point of purchase, and the export is built to the layout your BIS import already accepts.
Will BIS add an API?
The vendor has published no developer documentation, and we do not speculate on roadmaps. Today, matched CSV import is the supported path, and it is the one Vergo builds to.
Does Builder Information System have an API?
No. BIS publishes no public API — no read or write access and no developer documentation. It is a desktop product with locally held data.
How does Vergo connect to BIS?
Through custom-built CSV exports matched to BIS's import format. Job-coded card transactions are exported from Vergo and imported into BIS.
Can card spend flow into BIS job cost reports?
Yes. Transactions are coded to jobs and cost codes in Vergo before export, so imported entries carry full job costing into BIS reporting.
Does the desktop deployment change anything?
Only that a cloud API is not on the table. The import runs on the machine where BIS lives, using the file Vergo generates.
