App Creation
How to create an app, choose scopes, and prepare for authentication.
Create New App
- If you already have a Digits account: open Developer (left sidebar), click Create App
Get connected during the API preview
For a free developer account, sign up at my.digits.com/join/developer.
We'd love to learn more about what you're building! Reach out to [email protected] and let us know how we can help meet your needs.
Setting Identity
Identity
| Field | Description |
|---|---|
| App Name | The name of your app, shown in the Digits Dashboard and (eventually) to users |
| Tagline | A one-line summary of your app’s purpose |
| App Icon | Upload a logo for your app |
Your icon is the first thing users see. It appears on the Developer Dashboard, the install/auth screen, and (when available) your app listing. A clear, recognizable icon builds trust.
Summary
| Field | Description |
|---|---|
| Description | Clear overview of what your app does and who it’s for |
| Homepage | Your app’s public website or landing page. Must start with https:// |
| Support Email | The email address that end users should contact for app support |
| Developer Email | Where Digits can reach you for app-related updates or questions |
Choose App Permissions (Scopes)
| Scope | Description |
|---|---|
source:sync | Write source data into the Ledger |
ledger:read | Read data from the Ledger |
documents:write | Upload files to Documents |
Use least privilege—request only the scopes your app actually needs. You can adjust later, but changes may require re-authorization and/or regenerating credentials.
- Click Save.
Configure Redirects
Use Configuration to define your app’s Redirect URLs — the only URLs Digits is allowed to send users back to after an OAuth flow
Required for Authorization Code flow (e.g.,
https://yourapp.com/oauth/callback). Not required for Client Credentials. For full auth details, see Authentication
Requirements
- Full URL (scheme + host + path), e.g.
https://app.example.com/oauth/callback - HTTPS required in production (HTTP allowed for
localhost) - No wildcards (e.g.,
*example.comnot allowed) - No fragments (e.g.,
#sectionnot allowed) - Query strings are allowed, but must match exactly
- Trailing slashes must match (
/callback≠/callback/) - IPs not allowed;
localhostis allowed for local development
Use Add Redirect URI to include as many as you need
Keys
The Keys tab is where you manage your app’s credentials and publish-ready metadata
Environments
Use the toggle at the top of the page to select which credentials you’re viewing
Development — build & test only; installable in your Demo/Sandbox; no approval needed. See Developer Sandbox for install instructions!
Production — live use; initially installable only within your clients until approved/published; requires Install URL + Privacy Policy + Terms
Client Credentials flow (server-to-server)
See: Authentication for how to request a token and call the API
Production Metadata
When viewing the Production tab, you can provide additional fields:
These links appear during installation and are required for publishing_
- App Install URL:
https://link where users start your install/connect flow (usually kicks off OAuth). Example:https://example-app.example.com/install/digits - Privacy Policy: public URL to your policy
- Terms of Service: public URL to your terms
Updated 3 days ago