Does Landmark KEYPrime publish a public API?
No. Landmark Systems, the UK company behind KEYPrime, publishes no public API or developer documentation for the product. KEYPrime's release notes reference file-based routes for external data — such as bank statement CSV imports and exports for bookkeeping tools — but there is no open developer interface a third-party platform can build a live sync against.
KEYPrime is also deployed on-premise, which means there is no cloud endpoint to call even if an interface existed.
What does that mean for expense and card automation?
It means no card platform can honestly claim a direct API integration with Landmark KEYPrime. Farms and rural businesses running KEYPrime handle card spend the manual way: download statements, match receipts, code each line to the right enterprise or account, and enter or import the results. For a farm office juggling multiple enterprises and a busy season, that re-keying is real time lost.
How does Vergo connect to Landmark KEYPrime without an API?
Vergo uses the route KEYPrime actually supports: file import. Card transactions land in Vergo in real time, cardholders snap receipts from the field, and each transaction is coded as it is reviewed. Vergo then generates a custom-built CSV export matched to the import format KEYPrime expects, so the file loads cleanly instead of needing to be reshaped in a spreadsheet first.
The result: coding, receipts, and approvals happen in Vergo during the month, and KEYPrime receives one clean, ready-to-import file.
Is file import a workable long-term setup?
Yes — it is the same mechanism KEYPrime uses for bank statement data, so it fits how the system is designed to receive external transactions. The key is that the file matches KEYPrime's expected layout every time, which is exactly what Vergo's matched export is built to guarantee.
What changes for the farm office day to day?
The month-end scramble disappears in pieces. Receipts are captured in the field the moment a card is used, so nobody is reconstructing a purchase from a statement line six weeks later. Coding happens steadily through the month instead of in one sitting. And when it is time to post, the KEYPrime import file already exists — generated by Vergo in the right layout — rather than being assembled by hand in a spreadsheet. The office keeps its familiar KEYPrime import step; everything upstream of it stops being manual work. The result is a ledger that stays current through the season instead of catching up at close.
Does Landmark KEYPrime have an open API for developers?
No. Landmark Systems publishes no API or developer documentation for KEYPrime. The documented routes for external data are file-based, such as bank statement CSV import.
Can Vergo integrate with Landmark KEYPrime?
Yes, via files. Vergo provides custom-built CSV exports matched to KEYPrime's import format, so coded card transactions can be imported without manual re-entry.
Can bank feeds or card feeds connect directly to KEYPrime?
KEYPrime supports importing bank statement files rather than live third-party feeds. Card data follows the same pattern: it arrives by file, which is the route Vergo automates.
Who is this setup for?
UK farms and rural businesses running KEYPrime who want card spend coded with receipts during the month instead of re-keyed from statements at month-end.
