Sage API Guide for Contractors

One-line verdict: “Sage” is three different products with three different answers — and the one most contractors use has no cloud API at all. Openness: 2 / 5 — rated 2 because the headline contractor product, Sage 100 Contractor, offers no public cloud API, while the other two Sage products each come with their own gate or limit described below.

Start here: which Sage do you own?

This is the only page in the directory where the brand name is not enough. Before anyone quotes you an automation, you need to know which of these three products is actually running your books — the connection story is completely different for each.

Sage 100 Contractor — the relevant product for most small and mid-sized contractors: job costing, AIA billing, certified payroll. It has no public cloud API. What exists instead is a local API that runs on your own installation. To use it, an admin has to create a security group named exactly “API,” set up a per-company username and password, and accept that the connection consumes a licence use. The other proven route is a server-installed sync agent — software placed on your server that moves data on a schedule (the hh2 pattern). There are no webhooks, and no Zapier or Make app. In ladder terms: rungs 4–5 only — scheduled sync, or automation that runs on our side.

Sage Intacct — a larger product with a real REST API. The gate is money: app registration requires a paid Web Services licence (the client’s cost, surfaced before any build is priced). Usage runs on overage-metered Performance Tiers — charged for overages rather than blocked. Zapier is native here.

Sage Business Cloud Accounting — an open, free REST API with OAuth2 sign-in; contacts, quotes, invoices, and payments all read/write, plus native Zapier and Make. The limits are fit, not access: no job-costing objects, no sandbox (only 30-day trials), and US suitability UNVERIFIED — accounting-only until proven otherwise.

Can automate

• Back-office work and reporting on Sage 100 Contractor — workable as a scheduled-sync build: data moves on a timetable via the local setup or a sync agent, which suits job-cost and payroll rhythms that run daily or weekly rather than by the minute.
• Accounting automation on Intacct — with the Web Services licence in place, the REST API and native Zapier give invoicing and financial workflows a real connection.
• Everyday accounting on Business Cloud Accounting — contacts, quotes, invoices, and payments read/write, with both major bridges native — genuinely open, within its accounting-only scope.
• Invoice Chase / AR support — on any Sage product, the chase itself can run from synced balance data: read who owes what on a schedule, follow up from our comms layer.

Can’t automate

• Live, cloud-style automation on Sage 100 Contractor — it does not exist. No public cloud API, no webhooks, no bridge apps. Anything “instant” for a Sage 100 shop runs on our own calling and texting tools, with Sage updated by sync or by your team.
• Free API access on Intacct — the paid Web Services licence is required for app registration; there is no way around it and it belongs in the quote, in the open.
• Job costing in Business Cloud Accounting — no job-costing objects, so contractor cost workflows do not live there; and with US suitability UNVERIFIED, it should not be recommended to a US shop as a job-costing answer.
• Instant triggers anywhere in the Sage family as documented here — plan Sage automations on schedules and syncs, not on the second something happens.

Hidden gate: For the Sage most contractors own — 100 Contractor — the gate is that the cloud door was never built: access means a local installation change (a security group named exactly “API,” per-company credentials, a licence use consumed) or a sync agent on your server. For Intacct, the gate is a paid Web Services licence. Either way, the time to have this conversation is before a build is priced — never at go-live.

Build fit — what this platform supports

• Back-office / Reporting — the fit for Sage 100 shops: scheduled-sync builds, priced and promised as scheduled-sync builds.
• Invoice Chase / AR — supported from synced data on 100 Contractor; more directly connected on Intacct (with the licence) and Business Cloud Accounting.
• Speed-to-Lead, Missed-Call Capture, and Review Engine — these run on our comms layer for Sage 100 shops, exactly as they do for any closed platform — the floor works, it just is not a Sage integration.
• CRM Pipeline inside Sage — not a fit on the contractor product; pipeline belongs in a connected CRM.

What this means for your shop

A Sage 100 shop is not stuck — it is scheduled. Your automations will move at the speed of a sync, your live customer-facing responses will run on separate calling and texting tools on our side, and both facts should be written into any proposal in plain words. If your proposal says “Sage integration” without saying which Sage and which route, send it back.