Early access For SaaS builders and Sage partners
Planned: one Sage 100 integration for all your clients, not one per server.
If your product or your practice connects to Sage 100 for several clients, each one usually gets its own ODBC queries or Business Object Interface (BOI) scripts on its own server. Hundred is a planned REST API for Sage 100 that would replace that with one integration: your code would call one HTTPS endpoint, and a connector at each client would carry the call into their Sage 100. It is not built yet. Early access is open, and your answers decide what we build first.
- StagePlanned. Nothing is callable yet. We onboard teams in stages and email you when your modules are ready.
- PricePlanned: $99/month per connected Sage 100 company. Nothing is sold yet and no payment is taken. Planned pricing
- TodayA free read-only ODBC package and four integration guides. What exists today
What you maintain today, per client
| Route into Sage 100 | What it means when you have many clients |
|---|---|
| ODBC (SOTAMAS90) | Reads only: the driver is read-only. A DSN and a query job on, or next to, each client's Sage 100 server, in the right bitness. ODBC guide |
| Business Object Interface | The way to write with Sage 100's own validation, but it is a Windows COM interface: a script on each client's Sage 100 machine, and plan for a user license seat while a session is open. BOI guide |
| sData | Removed from Sage 100 in version 2025, so integrations that used it need another route. The remaining ones (ODBC, BOI, the SOAP-based eBusiness Web Services) all run on each client's own server. sData guide |
Each client becomes its own small integration project: its own server access, its own scripts, and its own fixes after Sage 100 upgrades.
What we plan for vendors and partners
PlannedYour client will install a small Windows service on the machine that runs Sage 100 and authorize the companies you may reach. Outbound HTTPS only: no open ports, no VPN.
Your code will call api.hundredapi.com with a company code, and Hundred will route each request to that company's connector. The same code for every client.
Writes will go through Sage 100's own business objects, so validation, numbering and posting rules apply as they do in the desktop client.
Planned endpoints: customers, sales orders, invoices, items and stock, vendors and purchase orders, and general ledger reads. The full list is on the home page, with request and response examples in the planned API docs. Missing a module your clients need? Tell us in the form below.
What exists today, and what does not
| Thing | What it is | Status |
|---|---|---|
sage100-odbc | A Python package that reads customers, open sales orders and items over ODBC. It runs where the ODBC driver runs, one install per client. Read-only. On GitHub | Free, read-only |
| Integration guides | ODBC, BOI, the sData removal and Shopify, each with its sources. Guides | Free |
| API docs | Endpoints, auth, errors and the connector design, published so you can check the fit before anything is built. Planned API docs | Published |
| REST API, connector, SDKs, writes | Not built yet. The early access list decides what comes first. | Planned |
Planned pricing
Planned · not on sale| Today | Joining the early access list is free and commits you to nothing. |
| Model | One subscription per connected Sage 100 company, covering the planned endpoints, read and write. Ten client companies would be ten subscriptions. |
| Your input | Tell us in the form whether this price works for you and how you would want to buy it. |
| Your client's Sage 100 | The connector signs in as one Sage 100 user and uses one license seat while it is connected. |
Join early access
Rolling out in stagesTell us what you build and for how many Sage 100 companies. We onboard teams in stages and email you when the modules you need are ready.