How to connect to Sage Business Cloud Accounting

Connecting takes one short flow in Apideck Vault: you pick the country your Sage Accounting account is in, sign in with your own Sage login, approve access, and choose which business the connection uses.

There are no credentials to copy and no client keys to paste. The application credentials were already configured by whoever built the integration, so your side of the handoff is only the sign-in itself.

Prerequisites

An active Sage Business Cloud Accounting subscription in Canada, the United Kingdom or Ireland. These are the three countries this connector authenticates. The country list in Vault shows seven Sage regions, because Sage Accounting is sold in more countries than this connector reaches — the others run on an older Sage API. Only Canada, the United Kingdom and Ireland complete authorization; selecting France, Germany, Spain or the United States will not connect.
A Sage user who is allowed to authorise applications — the account holder, or a user who has been granted that permission. If your user does not have it, ask the account holder to run the flow, or to grant you the permission first.
Know which Sage business this connection should use. You will select it at the end of the flow, and the connection is not usable until you do — including when your login can only reach one business.

Steps

Open Apideck Vault — either the hosted Vault link you were given, or the Vault screen embedded in the application you are connecting from.
Find Sage Business Cloud Accounting in the list of integrations and select Connect.
Under Select country, choose Canada, United Kingdom or Ireland, whichever matches your Sage account. This is required before you can authorise, and it decides which Sage sign-in you are sent to.
Select Authorize. Vault redirects you to Sage's own sign-in page.
Sign in with your Sage credentials and approve access when Sage asks you to confirm. Sage grants the integration a single permission, full_access, covering the Accounting data it reads and writes; there is no narrower scope to choose from.
You are returned to Vault and the connection shows as connected. Apideck stores and refreshes the tokens for you.
Set the Default Company. Open the connection's settings and pick the business this connection should use from the Default Company dropdown. The list is loaded live from the businesses your Sage login can see, which is why this step comes after signing in. Do not skip it when you only have one business: the setting is required either way, and the connection stays incomplete until it holds a value.

That is the whole flow. Reads and writes work once the connection shows as connected and the Default Company is set.

Your Sage credentials are entered on Sage's own sign-in page. They are used to complete the authorization and nothing else. They never reach the application you are connecting to, and Apideck does not store them.
Apideck holds tokens, not your password. Sage issues a short-lived access token plus a refresh token, and Apideck renews them in the background while the connection is in use. Nothing to maintain on your side.
A connection that sits unused expires. Sage's refresh token is valid for 31 days and is replaced each time it is used, so a connection that goes untouched for longer than a month has to be authorised again. Re-running the flow above restores it, and your Default Company selection is the only thing to confirm afterwards.

Revoking access

You stay in control. Open the connection in Vault and select Disconnect: Apideck sends the revocation to Sage, so the grant is withdrawn on Sage's side too and the integration can no longer read or write your Accounting data. You can reconnect later by running the same flow.

Troubleshooting

Authorization fails, or Sage never shows a consent screen. Check the country first: only Canada, the United Kingdom and Ireland authenticate on this connector, so a Sage Accounting account in another region cannot complete the flow even though the country list offers it. If the country is right, the likely cause is permission — see the next item.

Everything returns 403 Forbidden. Repeated 403s across every request mean the Sage user who authorised the connection does not have the role needed to authorise applications. Ask the account holder to authorise the connection instead, or to grant that user the permission, then reconnect in Vault.

The connection shows as connected but nothing works. Check the Default Company setting first: while it is empty the connection is treated as incomplete, whatever your login can reach. Open the connection's settings, select the business, and retry. If a business is already selected and requests still fail, the authorization has ended (see the 31-day note above) — reconnect in Vault.

The flow times out, or the link you were sent no longer works. Sage's authorization codes are single-use and short-lived, so a stale or already-used Vault link fails with an invalid-grant error. Start again from Vault rather than reloading the old page.

Data comes back from the wrong business. The connection uses the business chosen in Default Company. Change that selection on the connection rather than reconnecting — the same Sage login can be pointed at any business it has access to.

A write returns 405 Method Not Allowed, or a credit note refuses a second allocation. This is your Sage subscription tier rather than the connection: Sage's entry-level Start plan does not allow contact allocations and limits a credit note to one allocation. Everything else on the connection keeps working. Check your plan with Sage if you need those operations.

An error mentions invalid client credentials. That points at the application's Sage app registration, not at your account or your sign-in. Report it to whoever built the integration so they can check the credentials configured on their side.

Still stuck? Reach out to Apideck Support.