Does Ibcos Gold publish a public API?
No. Ibcos Gold, the dealership management system from Ibcos (part of Constellation's Vela group), does not publish a public API or an open developer portal. Ibcos has built specific connectors for named partners — a documented CLAAS connector exists, for example — but those are private, vendor-to-vendor integrations, not something a third-party product or your own IT team can build against. There is an "API Portal" reference in Ibcos material, but it is the backend for the Gold Service app, not documentation for outside developers.
What does no public API mean for expense automation?
It means no card or expense platform can claim a real-time sync into Ibcos Gold, whatever their integrations page implies. Gold typically runs on-premise on the dealership's own server, which makes cloud-to-system API connections harder still. Any platform telling you it "integrates" with Gold is, in practice, producing a file for you to import — the honest question is whether that file actually matches what Gold expects, or whether your accounts team ends up reworking it in a spreadsheet first.
How does Vergo work with Ibcos Gold without an API?
Vergo is built for exactly this situation. Card transactions are captured and coded in Vergo — receipt, supplier, nominal code, the coding your Gold setup uses — and Vergo generates a custom-built CSV export matched to the import format your Ibcos Gold system expects. Your bookkeeper runs the import inside Gold the same way they would any other batch. No rekeying transactions line by line, and no reshaping a generic bank-feed file to fit Gold's columns.
Is a CSV import workflow good enough?
For monthly card spend, yes — and it is the only automation path that is honest about how Gold actually works. The slow part of card reconciliation was never the file transfer; it is chasing receipts and coding each line. Vergo automates that part at the point of spend, so what reaches Gold is a clean, coded batch. The import itself takes minutes and stays fully in your team's control, which many on-premise Gold sites prefer anyway.
Could Ibcos open a public API later?
Ibcos could, but as of now there is no public developer documentation to build against, and we will not claim a sync that does not exist. If that changes, the import step gets replaced; everything upstream — cards, receipts, coding — stays the same in Vergo.
Does Ibcos Gold have a public API?
No. Ibcos Gold has no public API or open developer portal. Ibcos builds private connectors for specific partners (such as the documented CLAAS connector), but there is no published way for third-party software or your own developers to connect to Gold directly.
How does Vergo connect to Ibcos Gold?
Vergo provides custom-built CSV exports matched to the import format your Ibcos Gold system expects. Card transactions are coded in Vergo, exported as a ready-to-import file, and loaded into Gold as a normal batch import — no API required and no rekeying.
Does Gold being on-premise change anything?
It reinforces the file-based approach. Gold typically runs on the dealership's own server, so a file import your team runs locally is the natural fit — Vergo's export is built so that import needs no manual rework.
Can any expense platform sync to Ibcos Gold in real time?
No platform can honestly claim a real-time API sync into Ibcos Gold, because Gold publishes no API to sync against. File-based import is the working automation path, and Vergo builds its exports specifically to match Gold's format.
