Does Denovo CaseLoad have an API?
No — Denovo does not publish a public API for CaseLoad. Denovo, the Scottish legal software vendor behind CaseLoad, names specific technical integrations on its site, but those are partner arrangements, not open developer documentation. There is no public endpoint reference, authentication guide, or sandbox that a third-party product could build a live connection against.
What does no public API mean for expense automation?
It means no expense platform can honestly claim a real-time sync with CaseLoad. Any tool that says it "connects to CaseLoad" via API should be asked to show the developer documentation — there isn't any public documentation to point to. In practice, firms running CaseLoad move accounting data in and out through structured file imports, and expense automation has to work the same way.
For a legal cashroom that means the practical question is not "which API sync do we buy" but "how do we stop re-keying card and expense transactions into CaseLoad". The bottleneck is the manual entry: gathering receipts, coding each outlay to the right matter and client, and typing lines into the system one at a time.
How does Vergo work with CaseLoad without an API?
Through custom-built CSV exports matched to the import format CaseLoad expects. The flow looks like this:
- Fee earners and staff spend on Vergo cards; receipts and coding are captured at the point of spend.
- Vergo maps each transaction to the fields your CaseLoad import needs — date, amount, narrative, and the client or matter reference your cashroom codes against.
- You export a structured CSV built for CaseLoad and import it, instead of keying entries by hand.
This is deliberately not marketed as an API sync, because it isn't one. It is a file-based integration — the same mechanism CaseLoad itself supports — with the tedious part (formatting, coding, reconciliation prep) done for you.
Should you wait for a CaseLoad API before automating expenses?
There is no public roadmap suggesting one is coming, and firms have expense admin to run today. A matched CSV export removes most of the manual work now, and if Denovo ever publishes developer documentation, a live connection can be revisited then. Until that happens, treat any claimed API integration with CaseLoad with skepticism and use the import path the system actually supports.
What should a CaseLoad firm do next?
Audit how many hours your cashroom spends each month keying and coding card transactions, then compare that against a matched-file workflow: cards that capture receipts and matter coding as spend happens, and one prepared CSV import in place of line-by-line entry. The system's import mechanism does not change — the preparation moves out of the cashroom and into software built for it.
Does Denovo CaseLoad have a public API?
No. Denovo names specific technical integrations for CaseLoad, but publishes no public API documentation that third-party developers can build against.
How does Vergo integrate with Denovo CaseLoad?
Vergo provides custom-built CSV exports matched to the import format CaseLoad expects. Card transactions are captured and coded in Vergo, then imported into CaseLoad as a structured file — no manual re-keying.
Can card transactions be coded to matters before import?
Yes. Coding happens in Vergo at or after the point of spend, so the file you import into CaseLoad already carries the references your cashroom needs.
Is a file-based integration reliable enough for a legal cashroom?
File import is the mechanism CaseLoad itself supports for third-party data, and a matched export removes the error-prone step — hand-keying — rather than adding a new one.
