Connector library

Implemented source Enterprise, ERP & HR APIs

Sage 200 connector.

Read Sage 200 Professional UKI site/company, cost-centre and department references through five named OAuth actions.

Connector download

Download Sage 200

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Bearer token
Package size
10 KB
SHA-256
dab8ec6cead29ef9512fc1e871cf4b8de2f17884582a82e5063653b622291218

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Read Sage 200 Professional UKI site/company, cost-centre and department references through five named OAuth GET actions with explicit company scoping, selected metadata and exact int64 ID precision.

  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical readable HTTP scaffold, retained unchanged.

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

List site and company references

Read bounded site/company references visible to the issued token.

List cost centres

Read one bounded selected cost-centre page.

Get cost centre

Read selected metadata for one exact cost-centre ID.

List departments

Read one bounded selected department page.

Get department

Read selected metadata for one exact department ID.

Vendor API

API and access

Implementation considerations
  • Site and company references: Discover selected visible site/company pairs without guessed paging or complete-coverage claims.
  • Cost-centre references: Read one ordered reference page or an exact cost-centre ID with explicit company scope.
  • Department references: Read selected department IDs, codes and nullable names using the same native company-scoping contract.
  • Caller-managed GET reads; no transactions, writes or webhook triggers are included.
  • Use the fixed Professional UKI api.columbus.sage.com resource with a managed Bearer Token carrying an externally issued OAuth access token. Site discovery sends Bearer only; database reads additionally send X-Site and X-Company from the same returned reference row. Application authorization, token lifecycle and site/user access remain external. The current guide lists no subscription-key header; validate actual authorized gateway/app requirements before live use.
  • Reference pages send native $top, $skip, $orderby=id asc and $select=id,code,name. Page Size is a local 1–100 subset, default 50; Offset supports 0–100000. Caller owns further pages, pacing and consistency. Excess rows, duplicate/unordered IDs and malformed metadata fail without truncation; no next-offset, total count or full-directory claim is inferred.
  • Reference IDs preserve exact nonnegative signed-int64 strings up to 9223372036854775807; unsafe numbers and alternate integer spellings fail. Site tokens retain case/zeroes in a declared local ASCII subset without UUID assumptions. Company IDs use canonical nonnegative int32 values, retaining zero without assuming it identifies a usable company. Codes retain native spelling; empty names and null names remain distinct.
  • Professional UKI is the supported edition. Standard, other country editions, native Windows authentication and Sage Accounting/Intacct are separate contracts. No contact data, balances, transactions, arbitrary filters/hosts, writes or token issuance are included. Earlier scaffold mappings need deliberate migration with persistent identity preserved. Hosted import, executor support and live gateway/token/company/field/paging checks remain untested.
  • Five packaged Professional UKI OAuth GET reads use native site/company scoping, selected fields and ordered offset pages. Current vendor OpenAPI and request guides establish the contract; live app/gateway/site/company/token/permissions and paging require validation.

Support

Need help with Sage 200?

Tell us what you need to connect or change.