Does A-Systems JobView publish a public API?
No. A-Systems JobView is an on-premise construction accounting system, and A-Systems does not publish a public API for it. There is no developer portal, no documented endpoints, and no supported mechanism for a third-party application to push transactions into the JobView database.
JobView does offer an optional ODBC module, but it is read-only: it lets reporting tools query the database, not write to it. Read-only database access is useful for custom reports, but it does not give an expense platform a way to post credit card transactions, vendors, or job cost entries into JobView.
What does no API mean for expense automation?
It means no card program or expense platform can claim a live, two-way sync with JobView — any vendor implying otherwise is overstating what the system allows. In practice, card transactions reach JobView one of two ways: someone keys them in by hand, or they arrive as a file import in a format JobView accepts.
Manual entry is where most JobView shops end up by default. The bookkeeper collects statements and receipts, codes each charge to a job and cost code, and types the entries in. On a job-cost system, that coding step is the slow part — every charge needs a job, a cost code, and an account before it lands in the right place.
How does Vergo work with A-Systems JobView?
Vergo takes the file-import path and builds it out properly. Cardholders code their own transactions in Vergo — job, cost code, receipt — as they spend. Vergo then produces a custom-built CSV export matched to the import format JobView expects, so the file loads cleanly instead of needing manual cleanup first.
The result is not an API sync, and Vergo does not present it as one. It is a working automation path for an on-premise system that offers no other one: coding happens once, in the field, and the accounting team imports a ready file instead of rekeying a month of card activity.
Should you expect a JobView API later?
A-Systems has kept JobView an on-premise product with read-only ODBC as its extension point, and it has published no public API documentation. Teams choosing tooling around JobView today should plan around file-based integration rather than wait on an API that is not announced.
Does A-Systems JobView have a public API?
No. A-Systems does not publish a public API for JobView. The optional ODBC module provides read-only database access for reporting, but there is no supported write access for outside applications.
Can any expense platform sync directly with JobView?
No platform can offer a true API sync, because JobView does not expose one. The working integration path is a file import in the format JobView accepts, which is how Vergo connects.
How does Vergo get card transactions into JobView?
Cardholders code transactions to jobs and cost codes in Vergo, and Vergo generates a custom CSV export matched to JobView's import format. The accounting team imports the file instead of rekeying charges.
Does the ODBC module help with importing expenses?
Not for importing. ODBC access in JobView is read-only — good for pulling data into reports, but it cannot write credit card transactions or job cost entries into the system.
