Developer Sandbox

Digits has a demo environment with realistic data pre-loaded from other connections. Each Developer has access to their own individual resettable demo instance, illustrating both an accounting firm and a client.

Developers are able to add apps to their demo environment by performing an OAuth flow with their development client ID. The authorization process will install the app to the demo environment, enabling full API access to the demo instance.

✅

You'll need a developer account to use the Developer Sandbox.

Set one up today! https://my.digits.com/join/developer, and reach out to [email protected] to let us know what you're building.

Install & Test Your App

The OAuth authorization flow will automatically select your demo client when invoked with Development keys, enabling you to install your app to your development sandbox.

For example, initiate an OAuth authorization flow by directing a browser to the authorization endpoint:

https://connect.digits.com/v1/oauth/authorize?response_type=code
&client_id=<<your_client_id>>
&redirect_uri=<<your_app_redirect_url>>
&scope=source:sync ledger:read documents:write
&state=<<random_state_string>>

Once authorized, the app will be installed in your demo client, ready for initialization by making an API call to Sync Sources.

Access the Sandbox

1. From the Developer Dashboard, click Access Developer Sandbox.
2. Digits will automatically provision your sandbox environment (this takes a few moments).
3. Once ready, click to open your Developer Sandbox and start exploring.

Resetting your Sandbox

If you’d like a clean slate:

1. In your Developer Dashboard, find the Developer Sandbox tile.
2. Click the ⋮ menu → Reset Sandbox.
3. Confirm to restore all sample data.

🚧

Warning: Resetting deletes all test changes (uploads, edits, configs) and cannot be undone.

Sandbox Limitations

To keep this environment safe:

• Sample data only — no live bank or third-party connections
• Invitations disabled — you can’t invite collaborators to the Sandbox
• You can reset the sandbox, but not create multiple concurrent sandboxes