Does Evolution Mx publish a public API?
No. Evolution Mx, the construction accounting product from Integrity Software, does not publish a public API. There is no developer portal, no published endpoint reference, and no self-serve way for a third-party platform to read from or write to an Evolution Mx company file. The system runs in the cloud or on-premise, and data gets in the way it always has: through the application itself, or through file imports.
What does no API mean for expense automation?
It means no expense or card platform can claim a true two-way sync with Evolution Mx — any vendor implying transactions post directly into your ledger over an API is overstating what the system allows. In practice, teams running Evolution Mx handle card spend the manual way: download a statement, code each line to the right job and cost code, and key the batch in. That work scales with card volume, and it is where month-end delays usually come from.
How does Vergo connect to Evolution Mx without an API?
The honest path is file import. Vergo captures card transactions and receipts as they happen, your team codes them to jobs and cost codes inside Vergo, and Vergo produces a custom-built CSV export matched to the import format Evolution Mx expects. Your bookkeeper imports the file instead of typing entries line by line. It is not an API sync — no one can genuinely offer that for Evolution Mx today — but it removes the re-keying, which is the part that actually costs time.
What should Evolution Mx users look for in a card platform?
Look past the word "integration" and ask how the data physically arrives in Evolution Mx. If the answer is not a file built for Evolution Mx's importer, the answer is manual entry. Vergo's export is structured around the fields your import routine expects, so the batch loads cleanly with your job costing intact.
Does Evolution Mx have a public API?
No. Integrity Software does not publish a public API for Evolution Mx. There is no developer documentation or self-serve integration access for third-party platforms.
Can card transactions sync into Evolution Mx automatically?
Not over an API — no platform can offer that today. The working path is a structured file import: Vergo generates a custom CSV export matched to Evolution Mx's import format, which your team loads into the system.
How does Vergo work with Evolution Mx?
Vergo captures card spend and receipts, lets your team code transactions to jobs and cost codes, then produces a CSV export built for Evolution Mx's importer — replacing manual re-keying with a file import.
Does the connection work for both cloud and on-premise Evolution Mx?
Yes. Because the connection is file-based, it works the same whether Evolution Mx is deployed in the cloud or on-premise — the import is done inside the application either way.
