Connecting Digits

Digits uses OAuth 2.0, so connecting takes a sign-in and an approval: there are no credentials for you to copy, paste, or store.

Prerequisites

• A Digits account for the organisation whose ledger you want to connect.
• A user who can authorise third-party access to that organisation. Digits does not document a minimum role for this, so any user who is able to approve an app on the organisation's behalf can complete the connection.

Steps

1. Start the connection in Apideck Vault and click Authorize. You are redirected to Digits.
2. Sign in to Digits if you are not already signed in, and make sure you are signed in to the organisation whose ledger should be connected.
3. Review the access being requested. Digits shows you which application is asking and what it wants; this connector asks only to read ledger data from the organisation you authorised.
4. Approve the request. Digits sends you back to Vault, and the connection shows as Connected.

There is nothing to configure afterwards: the connector takes its ledger from the organisation you authorised.

Notes

• Your Digits login stays yours. You enter it on Digits' own sign-in page during the authorisation flow only. The application you are connecting to never sees your username, your password, or any other Digits credential: it receives only the access Digits grants on your behalf. See Digits' authentication documentation for how that grant works.
• The connection keeps itself alive. Apideck refreshes the Digits access token automatically in the background, so a working connection stays working without you re-authorising on a schedule.
• You stay in control of the grant. You can revoke this access from your own Digits account at any time by removing the application from the organisation that granted it. Revoking stops the connection from being renewed: no new access is issued after that point, so the connection stops working once the access already in flight expires. To restore it, authorise the connection again in Vault.

Troubleshooting

Issue	What to do
You closed the Digits window, clicked cancel, or the authorisation page timed out	Nothing is broken and nothing was granted. Start the connection again from Vault and complete the approval in one pass.
You authorised the wrong Digits organisation	Disconnect the connection in Vault, sign in to Digits as the correct organisation, then authorise again. A connection is tied to the organisation that approved it, so re-authorising is the way to move it.
Digits says the application cannot be installed into your organisation	Digits requires an application to be approved before it can be installed into organisations beyond the application owner's own. This one is resolved by the application owner, not by you: let them know which organisation you tried to connect, and ask them for an expected timeline. Your own sign-in and permissions are not the problem.
The connection reports as connected but the data you expect is missing	Confirm the ledger data exists in the Digits organisation you authorised, since the connection reads only that organisation. If it does, contact Apideck Support.