Does CYMA publish a public API?
No. CYMA does not publish public API documentation. It does list around twenty named technical integrations with specific partner products, and its documentation covers import and export dialogs — but a named partner integration is not the same as an open API. There are no published endpoints, no developer reference, and no documented way for an outside application to connect programmatically. CYMA runs on an Actian PSQL database, but direct database access is not something CYMA documents for third parties.
What does that mean for expense automation?
Without a public API, no expense platform can offer a documented direct sync into CYMA. The integration surface CYMA actually documents is its import/export capability — data comes in as structured files through CYMA's import dialogs. That shifts the automation question from "can a tool push into CYMA" to "can a tool produce a file CYMA imports cleanly."
How does Vergo work with CYMA?
Vergo integrates through custom-built CSV exports matched to CYMA's import format. Card transactions are captured in Vergo with receipts attached and coding applied — to departments, accounts, or whatever structure your CYMA chart uses — and then exported as a structured file for import into CYMA. Because CYMA is an on-premise system, the file-based path also fits how it is actually deployed: your bookkeeper imports the file into your local installation on your schedule.
Is a file import a real integration?
For card spend, yes. The labor in expense workflows is collecting receipts, coding transactions, and reconciling — not the transfer itself. Vergo does that upstream work on the card side, so the import into CYMA is a delivery step rather than a data-entry project. The outcome matches what an API sync would give the bookkeeper: coded transactions in CYMA without retyping.
Do CYMA's existing integrations change this?
They show CYMA can connect to specific partner products, but each is a bespoke arrangement, not an open interface. For any tool outside that named list, the documented path in is CYMA's import capability — which is the path Vergo builds for.
Does CYMA have a public API for developers?
No. CYMA lists named partner integrations and documents import/export dialogs, but publishes no public API or developer documentation.
How does Vergo integrate with CYMA?
Through custom-built CSV exports matched to CYMA's import format. Coded card transactions leave Vergo as a structured file your bookkeeper imports into CYMA.
Can Vergo connect to CYMA's Actian PSQL database directly?
No — CYMA does not document third-party database access, and Vergo does not claim it. The documented, supported path is file import, which is what Vergo uses.
Does the on-premise deployment cause problems?
No. The file-based workflow suits on-premise systems: Vergo generates the export in the cloud, and the import happens in your local CYMA installation whenever you run it.
