Sage Business Cloud

Back to Platform Coverage

Endpoints
GET
/accounting/accounts
POST
/accounting/accounts
GET
/accounting/accounts/{id}
PATCH
/accounting/accounts/{id}
DELETE
/accounting/accounts/{id}
GET
/accounting/balance_sheets
GET
/accounting/bank_feeds/accounts
POST
/accounting/bank_feeds/accounts
GET
/accounting/bank_feeds/accounts/{id}
POST
/accounting/bank_feeds/otp
GET
/accounting/bank_feeds/transactions
POST
/accounting/bank_feeds/transactions
GET
/accounting/bank_feeds/transactions/{id}
POST
/accounting/bill_credit_applications
GET
/accounting/bill_credit_memos
POST
/accounting/bill_credit_memos
GET
/accounting/bill_credit_memos/{id}
GET
/accounting/bill_payments
POST
/accounting/bill_payments
GET
/accounting/bill_payments/{id}
GET
/accounting/bills
POST
/accounting/bills
GET
/accounting/bills/{id}
PATCH
/accounting/bills/{id}
GET
/accounting/cash_flow_statements
GET
/accounting/company_info
GET
/accounting/currencies
GET
/accounting/currencies/{id}
GET
/accounting/customers
POST
/accounting/customers
GET
/accounting/customers/{id}
PATCH
/accounting/customers/{id}
DELETE
/accounting/customers/{id}
GET
/accounting/income_statements
GET
/accounting/items
POST
/accounting/items
GET
/accounting/items/{id}
PATCH
/accounting/items/{id}
DELETE
/accounting/items/{id}
GET
/accounting/payment_methods
GET
/accounting/payment_methods/{id}
GET
/accounting/reports
GET
/accounting/tax_rates
GET
/accounting/tax_rates/{id}
GET
/accounting/vendors
POST
/accounting/vendors
GET
/accounting/vendors/{id}
POST
/acp/{merchantId}/checkout_sessions
GET
/acp/{merchantId}/checkout_sessions/{id}
POST
/acp/{merchantId}/checkout_sessions/{id}
POST
/acp/{merchantId}/checkout_sessions/{id}/cancel
POST
/acp/{merchantId}/checkout_sessions/{id}/complete
GET
/auth/verify
GET
/configs/sync/connections/{id}
POST
/configs/sync/connections/{id}
PATCH
/configs/sync/connections/{id}
DELETE
/configs/sync/connections/{id}
GET
/configs/sync/platforms/{platform}
POST
/configs/sync/platforms/{platform}
PATCH
/configs/sync/platforms/{platform}
DELETE
/configs/sync/platforms/{platform}
GET
/configs/webhooks
GET
/configs/webhooks/{id}
GET
/configs/webhooks/{id}/platform_data_config
PATCH
/configs/webhooks/{id}/platform_data_config
GET
/connections
PATCH
/connections/{id}
DELETE
/connections/{id}
GET
/connections/access_token
POST
/connections/access_token/invalidate
POST
/connections/backfill
POST
/connections/create
POST
/connections/incremental_sync
GET
/connections/status
GET
/events
POST
/item/public_token/exchange
GET
/jobs/{id}
GET
/logs/requests/{id}
GET
/logs/webhooks
GET
/logs/webhooks/{id}
PATCH
/supplier_enablement/card_activations/{id}
POST
/supplier_enablement/merchants/{id}/card_activations
GET
/supplier_enablement/merchants/{id}/enrichments
PATCH
/supplier_enablement/merchants/card_activations/{id}
GET
/supplier_enablement_enrichments
POST
/ucp/{merchantId}/checkout-sessions
GET
/ucp/{merchantId}/checkout-sessions/{id}
PUT
/ucp/{merchantId}/checkout-sessions/{id}
POST
/ucp/{merchantId}/checkout-sessions/{id}/cancel
POST
/ucp/{merchantId}/checkout-sessions/{id}/complete

Accounts

Accounts support creation, updates to name and nominal code, and deletion of unused ledger accounts. Sage can reject deletion of protected accounts or accounts with dependent records; those errors are returned without falling back to deactivation. Ledger-account deletion was observed on the UK trial, but is not listed in Sage's public v3.1 reference.

Creation requires a name (1-200 characters), a nominal code containing digits and representing an integer from 1 to 99999999, and a supported account type. Nominal codes are sent to Sage as integers, so leading zeroes are not retained. Supported types are bank, other_current_asset, fixed_asset, other_asset, other_current_liability, long_term_liability, equity, income, other_income, and expense. Generic expenses use Sage's OVERHEADS subtype. Use other_current_liability for a general-ledger card clearing account; this does not create a credit-card banking resource. Similarly, bank creates an unattached BANK ledger, not a bank account.

Updates preserve omitted fields. A supplied name updates both Sage's internal name and chart display name, but does not rename a linked banking resource. Account type, deactivation, parent accounts, currency, subsidiaries and banking details are not supported on these write endpoints. Sage's own nominal-code availability and account-type restrictions still apply.

Currencies

Currency list and detail endpoints return Sage's read-only reference catalog, not a list of business-enabled expense currencies. Catalog membership does not guarantee that a currency can be used on an expense in the connected business.

currency_code contains Sage's currency identifier (for example, AUD), and currency_name contains its display label (for example, Australian Dollar (AUD)). The id field is a Rutter UUID, not the Sage currency code. No currency symbol is returned.

Sage does not provide currency creation or update timestamps. created_at is null, and the versioned API returns an empty string for updated_at. Sync re-fetches the reference catalog using pagination rather than an update-date filter.

Payment Methods

Sage Business Cloud connections support listing payment methods and retrieving a payment method by its Rutter ID through GET /accounting/payment_methods and GET /accounting/payment_methods/{id}.

Payment methods are read-only reference data. platform_id contains Sage's symbolic identifier (for example, CREDIT_DEBIT), and name contains its display label (for example, Credit/Debit Card). The id field is a Rutter UUID, not the symbolic Sage identifier.

Sage does not provide creation or update timestamps for payment methods, so created_at and updated_at are null. Incremental sync re-fetches the list rather than using a platform update-date filter.

Items

Item endpoints combine Sage's non-stock products and services. The Rutter id is a UUID; platform_id is Sage's resource-qualified path, such as /products/{sage_id} or /services/{sage_id}. Updates and deletes route to that same resource. Stock-item creation and product/service type changes are not supported.

Creating an item defaults to non_inventory; use type: "service" for a service. Both require invoice_item.account_id. Non-inventory products also require bill_item.account_id. These are Rutter account IDs from the existing Accounts GET endpoint. Sage may impose additional account eligibility rules.

Sage uses one description for both name and invoice_item.description. When both are supplied, they must match. bill_item.description maps to the separate purchase description, and bill_item.unit_price maps to cost_price. Names and item codes support 255 characters; purchase descriptions support 250. Accepted strings are preserved without trimming or truncation.

Rutter exposes the first returned sales-price/rate tier as invoice_item.unit_price. On creation, a supplied selling price uses the first active native price/rate type in API order and is tax-exclusive. Updates change the first existing tier and resend the other tiers with their names, amounts, type IDs and tax-inclusion flags. Sage does not document a universal default tier or guarantee nested price-row ID stability on updates. Omitted prices, accounts and status remain unsent during PATCH. Setting status to archived requests active: false; native restrictions still apply.

Incremental sync filters each catalog resource independently with updated_or_created_since. A product page does not advance the service cursor. Deleting a used item can be restricted by Sage; Rutter surfaces the native failure rather than archiving the item or trying another resource.

Bill GET links product/service references when Items have been synced for the connection. Bill POST/PATCH catalog-item selection remains a separate follow-up; item CRUD alone does not add write-side bill selection.

Have questions?

Contact support for personalized guidance.

Contact support