Does Condo Manager have a usable public API?
Not one a third party can build against. Condo Manager's site talks about APIs in marketing terms — explaining what an API is — but publishes no developer documentation: no endpoint reference, no docs link, no portal where an outside platform could register and integrate. Named connections that do exist, such as payment and banking-file arrangements, are specific vendor hookups (SparcPay, LeapAP, NACHA and lockbox banking files), not an open interface for expense software.
For integration purposes the honest summary is: no public API is available to connect to.
What does that mean for management company card spend?
Property management companies running community association books in Condo Manager often carry card spend across many associations — maintenance supplies, utilities set-up, site expenses. Without a public API, none of that can flow into Condo Manager automatically from a card platform. The transactions have to be entered or imported, allocated to the right association and GL account, and reconciled against the card account.
How does Vergo work with Condo Manager?
Vergo automates everything up to the import. Card transactions are captured with receipts at the point of spend and coded the way your books are organised — by association and GL account. When you're ready to post, Vergo generates a custom-built CSV export matched to the import format Condo Manager expects. Download, import, reconcile.
To be precise about the claim: this is a file-based path, not an API sync — no verified public API exists for anyone to sync with. The value is that the file arrives already shaped and already coded, so posting card spend stops being a data-entry project.
Could a real API appear later?
If Condo Manager publishes actual developer documentation, a direct connection would be worth evaluating. Until endpoints and docs exist publicly, integration decisions should rest on the working path: matched file import.
What should a management company verify before buying an expense tool?
Press any vendor claiming a Condo Manager connection on specifics: which documented endpoints does it call? There are none published, so the claim cannot be verified — and unverifiable integrations fail at month-end, not in the demo. The claim worth testing is the file: ask to see an export imported against your own association and GL structure. That is the claim Vergo makes and the test it invites, because the matched CSV path works with the import capability Condo Manager actually ships.
Doesn't Condo Manager's website mention an API?
It mentions APIs in general marketing terms, but publishes no developer documentation — no endpoints, no docs link. There is nothing a third-party platform can verifiably build against.
What integrations does Condo Manager actually name?
Specific payment and banking arrangements — SparcPay, LeapAP, and NACHA/lockbox banking files — which are vendor-specific hookups, not an open API for expense software.
How does Vergo get card spend into Condo Manager?
Via custom-built CSV exports matched to Condo Manager's import format, carrying the period's approved card transactions with their association and GL coding.
Can spend be split across associations?
Coding happens per transaction in Vergo, so each line carries the association and account it belongs to before it ever reaches the import file.



