Does Lexis Affinity publish a public API?
No public API is published for Lexis Affinity. Some third parties reference a REST interface running on a firm's own Affinity server, but the vendor publishes no open API documentation a platform can build a supported integration against. Affinity was acquired by Dye & Durham from LexisNexis in August 2024, and no public developer program has been published under either owner.
Affinity is deployed on-premise on the firm's own infrastructure, which also means there is no cloud endpoint for an external platform to reach.
What does that mean for law firm expense automation?
It means no card platform can claim a supported, direct API sync with Lexis Affinity. Firms running Affinity handle card spend manually: statements are downloaded, receipts chased across fee earners, and each line coded — including disbursements that belong on a matter — before being entered into the practice management system. That lag delays both the general ledger and matter-level cost recovery.
How does Vergo work with Lexis Affinity without an API?
Through matched file imports. Card transactions land in Vergo in real time; fee earners attach receipts from their phone; the accounts team codes each line as it arrives — office expenses to the ledger, matter-related spend flagged for the right matter. Vergo then generates a custom-built CSV export matched to the import format Affinity expects, ready to load as a batch.
The coding, receipts, and approvals happen in Vergo during the month; Affinity receives clean, structured data instead of a statement for the accounts team to re-key.
Is file import a sound approach for a legal accounts team?
Yes. For a system with no published API, a matched import file is the working automation path, and it fits how on-premise practice management systems take external batch data. Vergo builds the export to Affinity's specific layout, so the accounts team is not reworking columns each month — and the receipt trail stays in Vergo for audit.
What should firms evaluating card platforms ask?
Ask any vendor claiming an Affinity integration to show exactly how data moves, because with no published API the only honest answers involve files. Then ask where the coding happens: a platform that hands you a generic bank export leaves the matter allocation and spreadsheet rework on your accounts team, while a matched export — built to Affinity's import layout, with matter and ledger coding done at the point of spend — removes the manual work rather than relocating it. That difference, not the import click itself, is what determines how much time the firm actually gets back.
Does Lexis Affinity have a public API?
No public API is published. Third parties reference a REST interface on a firm's own Affinity server, but neither LexisNexis nor Dye & Durham publishes open API documentation for supported third-party integrations.
Who owns Lexis Affinity now?
Dye & Durham acquired Affinity from LexisNexis in August 2024. No public developer program has been published under either owner.
Can Vergo integrate with Lexis Affinity?
Yes, via files. Vergo provides custom-built CSV exports matched to the import format Affinity expects, carrying coded card transactions — including matter-related spend.
Can card spend be tied to matters?
Matter-related spend is flagged and coded in Vergo as it happens, so it reaches Affinity allocated rather than reconstructed from a statement weeks later.
