Connector Details
Overview
Sage 200 is a UK mid-market ERP for financials, inventory, and sales order processing. It is available as Sage 200 Standard and Sage 200 Professional (formerly Sage 200 Extra). It is a distinct product from Sage 50 UK, Sage 100, and Sage 300. The hotglue Sage 200 connector writes data through the Sage 200 REST API. Read syncs are not supported. hotglue supports both Sage 200 Standard and Sage 200 Professional. The two variants use different API roots — selecting the wrong one typically surfaces as “no sites found” during authorization rather than at request time.Credentials Setup
Follow the steps below to get the credentials you need to use the Sage 200 connector.1. Request OAuth client credentials
Sage 200 uses Sage ID OAuth 2.0 (authorization code grant). Client credentials are not self-serve in a developer console.- Request Confidential (web) API credentials from Sage Developer Support.
- Ask for separate development and production credentials if you need both environments.
- When requesting credentials, register the redirect URI
https://hotglue.xyz/callback. - Sage returns a
client_idandclient_secretby email.
2. Ensure the tenant API is reachable
For on-premise Sage 200 Professional, the Native API must be published (typically via Microsoft Entra Application Proxy) and registered with Sage Business Services. Sage 200 Standard Online is already cloud-hosted. A useful connectivity check after linking is a successfulGET /sites response for the authenticated Sage ID. Each site entry includes the site_id and company_id values the connector needs.
3. Tenant connection fields
After OAuth, tenants (or your flow config) must provide:
Optional connector settings:
Supported Objects
Write
The Sage 200 connector supports writing the objects below. Records are processed in dependency order: product categories → products → customers → documents.Sage has no native upsert endpoint. By default the connector looks up customers and products by their natural key and only creates missing records. Matched records are left unchanged unless
update_existing_records is enabled. Documents skip create when a matching posted transaction or analysis code already exists.ProductCategories
Payload file:ProductCategories.json
Looks up an existing product group by code. Product groups generally cannot be created through the API on many sites; missing groups are skipped and products fall back to default_product_group when configured.
Sample payload
Sample payload
Products
Payload file:Products.json
Creates products under an existing product group. Product type is inherited from the product group in Sage and cannot be set on the product itself.
*Required unless
default_product_group is set and can resolve the group.
Sample payload
Sample payload
Customers
Payload file:Customers.json
Sample payload
Sample payload
Invoices / CreditNotes
Payload files:Invoices.json / CreditNotes.json
These post to the sales ledger (/sales_invoices, /sales_credit_notes). They are financial summaries (goods + tax totals) against the customer account — not printable SOP invoices with product lines. Posted documents appear under Transaction Enquiry.
There is no Sage 200 API for multi-line SOP invoices. Prefer import_as_sales_orders / import_credits_as_sales_returns when line-item detail must appear in Sage.
Ledger invoices/credit notes post to the customer account immediately. SOP orders/returns do not affect the ledger until processed in Sage.
Sample payload
Sample payload
SalesOrders / SalesReturns
Payload files:SalesOrders.json / SalesReturns.json
These post SOP documents (/sop_orders, /sop_returns) with real product lines. Both endpoints take the same body; direction is determined by the document type, not the sign of quantities.
Sample payload
Sample payload