Does esiLaw 360 have a public API?
No. esiLaw 360, the hosted legal accounting platform from Dye & Durham (previously known as Unity Accounting), does not publish a public API. There is no developer host and no public API documentation for the product; the integrations Dye & Durham names for it are connections to its own products, not an open interface for third-party software.
What does that mean for law firm card spend?
Expense platforms that integrate over public APIs cannot connect to esiLaw 360. For Canadian firms running it, card spend — filing fees, process servers, travel, office purchases — comes in as a statement that bookkeeping codes by hand: which charges are firm overhead, which are client disbursements, and which matter each disbursement belongs to. Getting a disbursement onto the wrong matter means an unbilled cost or an awkward client conversation, so the coding is careful, and slow.
How does Vergo work with esiLaw 360 without an API?
Through file import, the mechanism the platform supports. Vergo provides custom-built CSV exports matched to the import format esiLaw 360 expects. Lawyers and staff code card purchases in Vergo when they spend — matter for disbursements, GL account for overhead — with the receipt attached. Bookkeeping reviews and exports a structured file that loads into esiLaw 360. There is no API sync to claim; the integration is honestly and deliberately file-based.
Why does point-of-purchase matter coding help a firm?
Because the person who paid the court fee knows which matter it belongs to, and at month end nobody else reliably does. Coding at purchase captures the matter while the context exists, which means disbursements make it onto client bills instead of dying in overhead.
What is the bottom line?
esiLaw 360 publishes no public API today, so file import is the working automation path — and Vergo's integration is built on a CSV matched to what esiLaw 360 imports.
What should a firm ask an expense vendor about esiLaw 360?
Ask whether the integration uses a public API — esiLaw 360 publishes none, so a sync claim needs explaining. Ask whether the export matches esiLaw 360's import format or leaves your bookkeeper reformatting a generic file every month. And ask the legal-specific question: can cardholders code a purchase to a client matter at the point of sale? A card tool that only understands GL accounts will leak disbursements into overhead. Vergo's answers: file-based and explicit about it, format-matched to esiLaw 360, and matter-aware coding at the moment of purchase.
Does esiLaw 360 have a public API?
No. There is no public developer documentation or API for esiLaw 360. Dye & Durham's named integrations for it are with its own products, not an open third-party interface.
Can Vergo integrate with esiLaw 360?
Yes, via file import. Vergo provides custom-built CSV exports matched to the import format esiLaw 360 expects, so coded card transactions load without manual keying.
Can card purchases be coded to client matters?
Yes. Cardholders code disbursements to the correct matter in Vergo at the point of purchase, so billable costs reach client bills instead of getting lost in overhead.
Is esiLaw 360 the same as Unity Accounting?
Yes — esiLaw 360 is the renamed Unity Accounting platform under Dye & Durham. The no-public-API picture applies to the platform under both names.
