Does ECI Spruce have a public API?
No. ECI Spruce, the hosted business management system for building materials dealers and lumberyards, does not publish a public API. There is no developer portal or public API documentation for Spruce, which means third-party software cannot read from or write to a Spruce company file over a documented interface.
What does no API mean for expense automation?
Most corporate card and expense platforms build their accounting integrations on public APIs. When a system does not publish one, those platforms typically cannot support it at all — Spruce users get left with manual entry: downloading a card statement, retyping each purchase into Spruce, and coding it to the right general ledger account by hand. For a dealer running dozens of company cards across yard staff, drivers, and outside sales, that is hours of month-end keying.
How does Vergo work with ECI Spruce without an API?
Vergo takes the path Spruce actually supports: file import. Vergo provides custom-built CSV exports matched to the import format Spruce expects. Cardholders capture receipts and code purchases in Vergo, and the finance team exports a structured file that loads into Spruce — no retyping, no reformatting in a spreadsheet first. It is not an API sync, and Vergo does not claim one; it is a working automation path built on the mechanism Spruce provides.
What does the workflow look like day to day?
Employees swipe Vergo cards for materials, fuel, and job supplies. Vergo collects the receipt and the coding — the GL account and any tracking fields your Spruce chart uses — at the point of purchase. At whatever cadence you close (daily, weekly, or at month end), you export the coded transactions from Vergo as a CSV built for Spruce and import it. The books reflect card spend without anyone keying individual transactions.
Could Spruce add an API later?
ECI Solutions maintains APIs for some of its other products, but as of this writing there is no public API published for Spruce. If that changes, a direct connection becomes possible; until then, format-matched CSV import is the reliable route, and it is the one Vergo has built for.
What should a Spruce dealer ask any expense vendor?
Three questions cut through the marketing. First: does your integration use a public API, and if so, whose — because Spruce does not publish one, an API claim deserves scrutiny. Second: does your export match Spruce's import format out of the box, or will my bookkeeper be rearranging columns in a spreadsheet every month? Third: where does the coding happen — at the point of purchase by the cardholder, or after the fact by accounting? Vergo's answers: file-based by design, format-matched to Spruce, and coded at the swipe with the receipt attached.
Does ECI Spruce have a public API?
No. ECI Spruce does not publish a public API or developer documentation, so third-party tools cannot connect to it over a documented programmatic interface.
Can Vergo integrate with ECI Spruce?
Yes, via file import. Vergo provides custom-built CSV exports matched to the import format Spruce expects, so coded card transactions load into Spruce without manual retyping. It is a file-based integration, not an API sync.
How do card transactions get into Spruce with Vergo?
Cardholders code purchases and attach receipts in Vergo. Finance exports a structured CSV built for Spruce's import format and loads it into Spruce on their normal close cadence.
Is a CSV import as good as an API sync?
It is not real-time, but for card spend it covers the job: transactions arrive fully coded with receipts attached, on the schedule you choose, with no per-transaction data entry.
