API & Integrations
Table of Contents

API & Integrations overview

Connect Diggle to your applications and identity provider.

Choose an integration

I want to…UseStart here

Automate projects and workspace user management

Workspace API

Getting Started

Synchronize users, workspace roles and offboarding from an identity provider

SCIM provisioning

Set Up SCIM Provisioning

Let users sign in with their Microsoft work account

Microsoft Entra SSO

Microsoft Entra SSO

Common use cases

  • Prepare training workspaces: create projects and assign existing or new workspace users through the API.
  • Manage joiners and leavers: provision users and remove workspace access through your identity provider.
  • Simplify sign-in: use Microsoft authentication while managing workspace access separately.

Workspace API, SCIM and SSO can be combined. SCIM manages users and workspace roles; private project assignment uses Diggle or the Workspace API.

Workspace API

Use workspace-scoped credentials to automate the supported project and user operations for that workspace. Start with a read-only request, then use the procedure reference before making changes.

SCIM provisioning

Provision users, assign workspace roles and deactivate managed workspace access through your identity provider. Start with the general setup guide, follow the Entra guide if applicable, then review the attribute reference and user lifecycle before enabling broader synchronization.

Enable an integration

Contact Diggle to enable Workspace API or SCIM. Include your workspace name and the integration you want to use. For Workspace API, also ask for the exact workspaceId. A workspace admin then creates the credential under Manage Workspace → Integrations.

Separate capabilities and credentials: Workspace API and SCIM are enabled separately. SCIM does not require Workspace API to be enabled. Use a Workspace API key for API procedures and a SCIM token for provisioning; neither is a Microsoft access token.

Troubleshooting

Identity and access

Microsoft SSO authenticates the user; it does not by itself grant workspace membership or override a local access block. Workspace roles and project grants determine access. Enterprise licensing follows qualifying membership, not simply an enabled integration or a pending invitation. Read these guides alongside the setup instructions: