Does Access COINS publish a public API?
No. Access COINS, the construction ERP from The Access Group, does not publish a public API. APIs for COINS exist as a licensed feature within Access's Enterprise bundle, but they are not publicly documented — there is no open developer portal where a third-party platform can read the endpoints and build a supported integration. Some vendors, such as Payapps and Earlytrade, have built integrations with COINS, but those run through commercial arrangements with Access rather than open API access.
What does that mean for expense automation?
It means no expense or card platform can offer an off-the-shelf API sync with COINS. Without open documentation, an integration has to go through Access's own licensing and partnership channel, and most card platforms have not. In practice, card transactions reach COINS the same way they reach most hosted construction ERPs without open APIs: entered by hand against contracts and cost heads, or brought in as a file import in a layout COINS accepts.
For a construction finance team, the manual path is the expensive one. Every card charge has to be coded to the right contract, cost head, and category, matched to a receipt, and keyed in — usually weeks after the purchase, by someone who was not on site when it happened.
How does Vergo work with Access COINS?
Vergo takes the file route and does the hard part for you. Cardholders code each transaction in Vergo at the point of spend — contract, cost head, receipt attached from a phone. Vergo then produces a custom-built CSV export matched to the import format COINS expects, so the file loads as a clean batch rather than a spreadsheet someone has to rework.
Vergo does not claim an API sync with COINS, because COINS does not make one publicly available. What Vergo provides is the working automation path: coding captured once in the field, and a ready-to-import file for the accounts team.
Could COINS API access open up?
Access keeps API capability inside its Enterprise licensing rather than publishing it, and integration details are available only through the Access partnership channel. Teams planning their card and expense tooling around COINS today should assume file-based integration is the dependable path.
Does Access COINS have a public API?
No. API access to COINS is a licensed Enterprise-bundle feature from The Access Group and is not publicly documented. There is no open developer portal for third parties to build against.
Haven't other vendors integrated with COINS?
A few have — Payapps and Earlytrade are named examples — but through commercial arrangements with Access, not open API access. That route is not available off the shelf to expense platforms.
How does Vergo get card spend into COINS?
Cardholders code transactions to contracts and cost heads in Vergo, and Vergo generates a custom CSV export matched to COINS's import format. The accounts team imports the file instead of rekeying charges.
Is a CSV import as good as an API sync?
It is not a live sync, and Vergo does not present it as one. But because coding happens at the point of spend, the import file arrives fully coded — which removes the rekeying and receipt-chasing that make manual card entry slow.
