Does NewStar publish a public API?
No. NewStar, Constellation's ERP for homebuilders, publishes no public API or developer documentation. There is no documented interface for a third-party expense or card platform to build a sync against.
What does that mean for a homebuilder's expense automation?
No card platform can honestly claim a direct sync into NewStar. Field spend — lumber-yard runs, subcontractor supplies, fuel, punch-list materials — cannot post into job costs automatically. It gets keyed in by the accounting team, or it arrives as a file NewStar can import. For builders running dozens of active lots, the manual version is a real month-end tax.
How does Vergo work with NewStar without an API?
Vergo automates the file route. Card transactions are captured as they happen and coded in Vergo — job, cost code, category — with the receipt attached from the field. Vergo then generates a custom-built CSV export matched to NewStar's import format, and your accounting team uploads it. Vergo does not present this as an API sync; it is the honest, working automation path for an ERP with no published API, and it ends in the same place: coded spend on the right jobs.
What should you ask a vendor claiming a NewStar integration?
Ask for the developer documentation the integration is built on — publicly, none exists. The comparison that matters between card platforms is whose export file matches NewStar's importer with the least cleanup, because that match is what your controller feels every close.
Why does this matter more for homebuilders?
Because homebuilding spend is field spend. The people making purchases — superintendents, purchasing managers, warranty techs — are on lots, not at desks, and the value of a card platform depends on getting each purchase onto the right job and cost code while the context is fresh. An ERP with no public API cannot receive that coding automatically, which is why so many NewStar builders still run month-end coding marathons from statements. Vergo's answer moves the coding to the field and the delivery to a file: the purchase is coded on a phone at the lumber yard, and the accounting team imports a matched CSV instead of reconstructing a month of spend. No API required, because none is published — and job-cost reports stop lagging a month behind the field.
In short: NewStar publishes no API today, and Vergo's matched CSV export is the dependable path that gets field spend onto jobs now — without waiting on Constellation's roadmap.
Does NewStar have a public API?
No. Constellation publishes no public API or developer documentation for NewStar, so there is no interface for third-party platforms to build against.
How do card transactions get into NewStar?
By file import. Vergo produces custom CSV exports matched to NewStar's import format, with transactions already coded to jobs and cost codes, so the upload is the only manual step.
Can field spend still be job-costed without an API?
Yes — coding happens in Vergo at the point of purchase, from the field, so the imported file carries job and cost-code detail rather than uncoded statement lines.
Does Vergo claim an API integration with NewStar?
No. Vergo states plainly that NewStar publishes no public API and connects through custom-built CSV exports instead.
