Does E2 Shop System have an API?
No. E2 Shop System, ECI Solutions' shop management software for job shops and make-to-order manufacturers, publishes no public API — neither read nor write access is documented for third-party developers. There is no endpoint reference or sandbox an outside product can build a live connection against.
What does no API mean for expense automation in a job shop?
It means no expense or card platform can honestly claim a real-time sync with E2. The system runs on-premise, and outside financial data gets in the way it does for most on-premise shop software: someone prepares a file in the shape E2's import expects, or keys entries in by hand.
For a shop, the pain is concrete. Card spend — tooling, perishable cutting tools, hardware runs, maintenance parts, freight — accumulates across a handful of cards, and at month end someone in the office reconstructs it from statements: matching receipts, deciding which purchases belong to which accounts or jobs, and typing it all in. That is hours of admin that has nothing to do with making parts.
How does Vergo work with E2 without an API?
Vergo provides custom-built CSV exports matched to the import format E2 Shop System expects:
- Shop and office staff spend on Vergo cards; receipts and coding are captured when the purchase happens.
- Each transaction is mapped to the fields your E2 import needs — date, amount, vendor, and the GL account coding your bookkeeper uses.
- You export a structured CSV built for E2 and import it, replacing manual entry from statements.
This is deliberately described as a file integration, not an API sync — E2 has no public API to sync through. The mechanism is the one the system supports; the difference is that the file arrives already formatted and coded.
Should a shop wait for E2 to add an API?
ECI has published no developer documentation for E2, and the card-spend admin exists now. A matched CSV export removes the re-keying today, and if that ever changes, a deeper connection can be looked at then. In the meantime, treat any tool claiming an API integration with E2 Shop System with suspicion — ask to see the docs.
What should a shop on E2 do next?
Add up the office hours spent each month keying and coding card spend, then compare a matched-file workflow: cards that capture receipts and GL coding at the point of purchase, and one prepared CSV import in place of manual entry. E2's import mechanism stays exactly as it is — the file preparation just stops being an office job.
Does E2 Shop System have a public API?
No. ECI Solutions publishes no API documentation for E2 — no read or write access is available to third-party tools.
How does Vergo integrate with E2 Shop System?
Through custom-built CSV exports matched to the import format E2 expects. Card transactions are captured and coded in Vergo, then imported into E2 as a structured file.
Can purchases be coded before they reach E2?
Yes. Cardholders code spend in Vergo as it happens, so the export already carries the vendor and GL account coding your import needs.
Does the on-premise deployment matter?
It confirms the file path. E2 runs on-premise, and file import works wherever the system is installed — no network integration project required.
