Available now · Sage 100 API

An integration platform for the ERPs you already run.

Documented REST APIs where an API is the right answer, starting with Sage 100. Where an endpoint is not enough, we build the integration on the platform underneath: schedules, transformations, retries.

The Sage 100 API Read the docs

What you get

An API where an API is enough

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 today. Sage 100 is the one you can also call yourself; for the others we build the integration and the API follows the same shape when it lands.

Not an ERP connector, but on the same account: the Alerts API is transactional email and a structured log store, for the moment one of these integrations needs to tell somebody it failed. Signup for it is self-serve.

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.

Talk to us about access