Skip to main content
Use the @bijection/connectors/sage-200 entrypoint to declare Sage 200 resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
API resource

​
observed: Keyset walk by (date_time_updated, id), read-only

The following example matches configuration standard.

​
Configuration: standard

Case: sage-200/resource/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: sage_200. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: professional

Case: sage-200/resource/observed/professional. Connection and resource configuration are declared by this exact case. Credential kind: sage_200. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

sage200.resource.observed({ edition, resource, columns, pageSize?, lag?, every? }) reads one list resource of Sage 200 (UK) through Sage’s hosted API: https://api.columbus.sage.com/uk/sage200/accounts/v1/ for Standard and .../sage200extra/accounts/v1/ for Professional, whose support provider must first enable the API for the on-premises installation. The binding’s setup names the site and company that GET /sites lists; every request sends them as X-Site and X-Company. Each page asks for rows strictly after the last (date_time_updated, id) read, $orderby=date_time_updated asc,id asc and $top pageSize (500 by default, at most 5,000 on releases after February 2019): date_time_updated gt T or (date_time_updated eq T and id gt K), with T the UTC instant unquoted as Sage’s filter page requires. Sage states no continuation, so a full page continues the walk. A finished pass carries the last pair and the next pass re-reads from lag seconds (default 300) before it, deduplicating by date_time_updated, which is the version. Limits: id is an int64 JSON number and amounts are JSON numbers, so columns are string, integer, number or boolean, never exact decimals. A date_time_updated finer than a millisecond is refused. Sage documents no deletion listing and no concurrency token, so deleted rows stay published and no command is declared. No rate limit is documented; 429 and 503 are transient. Bind a sage_200 credential: an oauth_refresh envelope for a Sage ID authorization-code grant at https://id.sage.com/oauth/token (scope openid profile email offline_access, audience s200ukipd/sage200), whose Sage ID is mapped to a Sage 200 user with access to the company. Access tokens last 480 minutes and the refresh token up to 90 days. No Sage 200 site has been reached.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.