What we do
Tools
Industries
Department
How we workLet's talk →
Home/Sage APIs by Product
Sage developer APIs

Sage APIs, Product by Product: Which Sage You Run Decides What You Can Build

A client says "we're on Sage" and you open the Sage developer portal to find a dozen products, each with its own docs. Sage Accounting has a cloud REST API. Sage 50 has a desktop SDK. Sage X3 speaks GraphQL. Sage APIs aren't one API with versions; they're separate interfaces for separate products, and the first job is matching the docs to the install.

Which Sage has which API

Access terms and versions change, so confirm the details on Sage's developer portal for your product before you build.

Sage product What a developer works with Good to know
Sage Accounting (cloud, small business) The Sage Accounting API v3.1: REST and JSON, with OAuth 2.0. One base URL for all supported countries, which are the UK, Ireland and Canada. Apps are registered through Sage's developer portal.
Sage Intacct A REST API, and the older XML Web Services API. Sage still supports the XML API but releases new objects and features on REST. Both need a web services developer subscription.
Sage X3 A GraphQL API, first released in the 2021 R2 update, plus SOAP web services for classic pages. Sage's GraphQL docs assume Sage's cloud. On-premise sites need Sage X3 Services installed before the endpoint answers.
Sage 300 (formerly Accpac) The Sage 300 Web API, a REST interface based on OData, alongside the long-standing Sage 300 SDK. The Web API is installed with the Sage 300 Web Screens. Sage's developer community doesn't host Sage 300, so use the product documentation.
Sage 100 The Business Object Interface (BOI), a COM interface to the same business logic the desktop uses, plus ODBC for reading data. BOI comes with Sage 100 activation and enforces Sage's own validations, so writes through it behave like a user entry.
Sage 50 US and Canada A desktop .NET SDK for each edition, a free download for developers. Code runs on a Windows machine with Sage 50 installed. There's no cloud endpoint to call from a web app.
Sage 50 UK Sage Data Objects (SDO), a COM library working against the company data. Access and the SDO help come with a paid UK Developer Programme subscription.

Building on whichever Sage interface you have

On the cloud products, Sage Accounting, Intacct and X3 in Sage's cloud, the work looks like any modern integration: OAuth or web services credentials, webhooks or scheduled pulls, and the business rules a prebuilt connector doesn't hold. On Sage 300 the Web API covers most of it, and the SDK fills in where an endpoint is missing.

On the desktop products the design changes. Sage 100's BOI and the Sage 50 SDKs run on a machine inside the client's network, so n-frames builds a small service there that talks to Sage locally and syncs with your web app or other systems over a secure connection. Where an older Sage 50 install has no write path for something, we read it through ODBC or the SDK and keep the write on the system that can accept it.

Weeks lost to the wrong Sage documentation

Each of these starts with docs that are correct for some Sage, just not the one in front of you.

Sage Accounting docs used for a Sage 50 job

How you'll know: OAuth works, calls return a business, but none of the client's data is there.

Fix: Sage Accounting is a different cloud product. A Sage 50 desktop company is reached through that edition's SDK or SDO, on the machine where the data lives.

A US Sage 50 SDK pointed at a UK company

How you'll know: The code installs and nothing connects.

Fix: Each regional Sage 50 is its own codebase. Confirm the edition on the About screen before picking the SDK.

New Intacct work started on the XML API

How you'll know: The object you need has no XML function, or only a limited one.

Fix: Start new Intacct builds on the REST API, where Sage now releases new objects, and keep XML for existing integrations until you move them.

X3 GraphQL calls to an on-premise install that times out

How you'll know: The examples in Sage's docs work on the demo, not at the client.

Fix: On-premise X3 needs Sage X3 Services installed and configured before GraphQL is available. Older classic pages may still need SOAP.

Looking for Sage Pay API docs

How you'll know: Every Sage Pay link redirects somewhere else.

Fix: Sage sold its payment gateway in 2020. Elavon bought it and renamed it Opayo, and it now runs under Elavon, so use Elavon's Opayo documentation.

Sage API questions, by product

Does Sage 50 have a REST API?

No. Sage 50 US and Canada offer a desktop SDK, and Sage 50 UK offers Sage Data Objects. Both run on a Windows machine with Sage 50 installed. If you need a REST endpoint, it has to be built as a service that sits beside Sage 50 and talks to it through the SDK.

Where do I find the Sage 100 API documentation?

Sage 100's developer material is on Sage's developer portal under Sage 100, and the Business Object Interface is covered in Sage 100's own help, including its BOI FAQs. BOI is provided as part of Sage 100 activation.

What was Sage Accpac, and does it still have an API?

Accpac is the earlier name of Sage 300. The SDK carried over from the Accpac days, and Sage 300 has since added a REST Web API, so older "Accpac integration" posts usually describe the SDK side of today's Sage 300.

Do I need a developer to build on a Sage API?

For anything in production, yes. Even on Sage's cloud APIs, handling authentication, errors, retries and your own business rules is real development work. On the desktop SDKs it also means running and maintaining software on a machine at the client.

Is Sage Pay the same as Sage accounting software?

No, and it's no longer a Sage product. Sage Pay was the payment gateway Sage owned until it sold the business in 2020. Elavon bought it in 2020 and renamed it Opayo, and it now runs under Elavon.

Who builds Sage API integrations?

n-frames does, across the cloud and desktop products: Sage Accounting and Intacct over their APIs, Sage 300 on the Web API and SDK, and Sage 100 and Sage 50 through a local service that runs next to the install.

Let's talk

One integration, built on the Sage you actually run

n-frames reads the product and version first, then builds on the interface that product really offers: a REST or GraphQL API on the cloud side, the SDK or BOI on the desktop side. Your other systems get the Sage data they need without anyone re-keying it.

Sage 50, 100, 300 or X3, connected →

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.