Does Merlin Business Software publish a public API?
No. Merlin Business Software, the UK on-premise system for distribution and retail businesses now owned by Aptean (acquired October 2022), publishes no API or developer documentation on any Merlin or Aptean domain. There is no public endpoint or schema a third-party expense platform can build against.
What does no published API mean for expense automation?
It means no card or expense platform can honestly claim a live sync into Merlin. Company card spend — trade counter purchases, fuel, consumables — cannot post into the ledger automatically. It is either keyed in by hand or brought in as a file Merlin can import. On-premise deployment reinforces this: even where private interfaces exist inside a customer's installation, nothing is published for outside products to connect to.
How does Vergo work with Merlin without an API?
Vergo automates the file route. Card transactions are captured and coded in Vergo — nominal code, department, category, receipt attached — and exported as a custom-built CSV matched to Merlin's import format. Your accounts team uploads the file into Merlin instead of re-entering each transaction. Vergo does not dress this up as an API sync; it is the honest, working path for a system with no published API.
What should you ask a vendor claiming a Merlin integration?
Ask to see the developer documentation the integration is built on. Publicly there is none, on Merlin's site or Aptean's. The practical comparison between card platforms is whose export file matches Merlin's importer with the least monthly cleanup — that is what your bookkeeper will feel.
Does the Aptean acquisition change the answer?
Not so far. Aptean maintains developer resources for some of its other products, but no API or developer page for Merlin exists on any Merlin or Aptean domain. Until documentation is published, a buying decision has to rest on what exists today: file import. That is why Vergo's Merlin connection is built as a matched CSV export rather than code against an interface nobody can see — it works now, depends on nothing in Aptean's roadmap, and keeps working as long as Merlin accepts imports. If Aptean does publish a Merlin API later, the transaction data in Vergo is already coded and structured; the delivery step could be upgraded without changing the workflow your accounts team runs. In the meantime, an honest file route beats an integration badge that cannot point at its documentation.
Does Merlin Business Software have a public API?
No. There is no API or developer page on any Merlin or Aptean domain, so no public interface exists for third-party platforms to build against.
Who owns Merlin Business Software now?
Aptean, which acquired Merlin Business Software in October 2022. The acquisition has not produced public developer documentation for Merlin.
How do card transactions get into Merlin?
By file import. Vergo produces custom CSV exports matched to Merlin's import format, with transactions already coded to your nominal structure, so the upload is the only manual step.
Does on-premise deployment change anything?
It reinforces the file route: an on-premise install has no published cloud endpoint for outside products to reach, so a matched import file is the reliable way in.
