Does Edmunds GovTech MCSJ have a public API?
No. Edmunds GovTech does not publish a public API for MCSJ. Its technical documentation lives behind a login-gated support portal, and there is no public developer site for the product. (The developer.edmunds.com site you may find in a search belongs to the unrelated car-shopping company.) Edmunds GovTech does maintain technology integrations with specific partners — NeoGov, Worldpay, Twilio, and Neptune/Sensus meter systems among them — but those are vendor-built connections, not an open interface other software can use.
What does that mean for purchasing card automation?
Card platforms that rely on public APIs cannot connect to MCSJ. For municipalities and local government entities running MCSJ on-premise, that has traditionally meant manual entry: pulling the p-card statement, coding each purchase to the correct fund, department, and account, and keying the batch into MCSJ. In a fund accounting environment where every transaction has to land in the right fund, that coding work is exacting and slow.
How does Vergo work with MCSJ without an API?
Through the mechanism MCSJ supports: file import. Vergo provides custom-built CSV exports matched to the import format MCSJ expects. Cardholders code purchases in Vergo against your account structure when they buy, finance reviews, and the export loads into MCSJ as a batch. Vergo does not claim an API sync with MCSJ — there is none to claim — but the file path automates the same work.
How does coding work for fund accounting?
Your MCSJ account structure is loaded into Vergo, so cardholders pick from your real funds, departments, and line items rather than free-typing. A public works purchase gets coded to the right fund and budget line at the point of sale, with the receipt attached. By the time the file reaches MCSJ, the allocation questions are already answered.
What is the honest bottom line?
MCSJ publishes no public API, so any vendor claiming a live sync should be met with questions. File import is the supported route, and Vergo has built its MCSJ integration on exactly that.
What should a municipality ask a card vendor about MCSJ?
Ask whether the integration is API-based or file-based — since MCSJ publishes no public API, an API claim should come with an explanation of whose interface it uses. Ask whether the export matches MCSJ's import format directly, or whether your finance office will be reformatting a generic file every cycle. And ask how the vendor handles fund and department coding — a card tool that only knows GL accounts will fight your chart, not fit it. Vergo's answers: file-based and honest about it, format-matched to MCSJ, and built to code against a municipal account structure.
Does Edmunds GovTech MCSJ have a public API?
No. There is no public API or developer documentation for MCSJ; technical resources are behind a login-gated support portal. Edmunds GovTech's named integrations (NeoGov, Worldpay, Twilio, Neptune/Sensus) are vendor-built partner connections, not an open API.
Can Vergo integrate with MCSJ?
Yes, via file import. Vergo provides custom-built CSV exports matched to MCSJ's import format, so coded card transactions load as a batch without manual keying.
Does the CSV path support fund accounting codes?
Yes. Your MCSJ funds, departments, and accounts are loaded into Vergo, and cardholders code against that structure at the point of purchase.
Does it matter that MCSJ is on-premise?
No. Because the integration is file-based, it works the same whether MCSJ runs on your own servers or hosted — you import the file the way you import any other batch.
