One integration surface for the ERPs you already run.
SConnect puts a documented HTTP API in front of your ERP, so the systems that need its data can stop scraping screens, stop trading CSVs and stop waiting for the nightly job.
What you get
An API, not a project
A documented HTTP surface with an OpenAPI spec behind it. Anything that speaks HTTP can read and write your ERP data — no per-integration adapter, no ODBC driver on someone else’s laptop.
Nothing opens in your firewall
The on-prem connector dials out over a WebSocket and keeps that connection open. There is no inbound rule to request, no VPN to stand up, and no port to explain to your security team.
Writes that survive a dropped link
Every write is persisted before it is dispatched. If the connector drops mid-flight, the work becomes a job you can query rather than a response you lost.
The ERPs
Martin and Associates implements and integrates all four. Sage 100 is the one you can call today; the others follow the same shape when they land.
-
Sage 100 Available now
39 readable entities across A/R, A/P, G/L, I/M, S/O and P/O, with reads, writes, an interactive playground and a downloadable Bruno collection.
-
Acumatica To follow
-
Sage Intacct To follow
-
Dynamics GP To follow
Proven before it was packaged
What you are buying was not written to be sold. SConnect is the framework Martin and Associates’ own client integrations already run on, so the code answering your requests was in production before it had a price.
It is also why the docs state the limits as plainly as the features. Anyone integrating against an ERP finds the edges by week two — better to read about them in week one.
Built and supported by Martin and Associates.