Build Centralized Agreement Hubs Using the Docusign Workspaces API

Fragmented agreement workflows create real friction: documents scattered across emails, no single place for clients or colleagues to track what needs their attention, and constant back-and-forth just to get signatures. 

The Docusign Workspaces API (beta) gives developers a way to build centralized, collaborative agreement hubs directly into their applications without coding any UI from scratch.

If you're familiar with other Docusign APIs, it's worth knowing how Workspaces fits in: Maestro handles workflow automation, and Navigator serves as an intelligent agreement repository. Workspaces is the central meeting place where participants come together to complete tasks. It works alongside whatever workflow mechanism you're using, whether that's Maestro or your own.

In this post, you’ll learn:

• What the Workspaces API is and why it matters

• Real-world use cases with sample app walkthroughs

• How to get started with a working sample app

Note: The Workspaces API is currently in beta. This means it's available for anyone to use today, but endpoints and behavior may change without notice until it reaches general availability.

What is the Workspaces API?

The Workspaces API (beta) lets you programmatically create and manage Docusign Workspaces. These secure digital hubs can aggregate envelopes, documents, and tasks for a specific person or team. 

The Workspaces API is built around these core objects and concepts:

• Workspaces – the central, digital hub where people, agreements, and related information come together and are managed.

• Users – individuals invited to collaborate in a workspace for a given agreement process.

• Roles and permission levels – definitions of what users can do in a workspace (for example, Manage vs Participate, internal vs external participants).

• Documents – the document files (PDF, Word, HTML, etc.) or envelopes that participants review, sign, or are tasked with uploading within the workspace context.

With the API, you can:

• Create workspaces dynamically

• Add documents, envelopes, and upload requests 

• Manage user roles and permissions

This allows you to add structured, collaborative engagement directly into your applications.

Why use Workspaces?

Agreement workflows often span multiple systems, inboxes, and participants. Without a centralized hub, developers end up stitching together notifications, document links, and task lists manually or leaving that coordination entirely to users. 

Workspaces move that coordination into the API layer, so your application can own the experience. 

Workspaces provides:

• Centralization: one place for all documents and tasks

• Automation: programmatic creation and management via API

• Reduced noise: fewer unnecessary email notifications

• Better user experience: clear visibility into outstanding actions

• Improved efficiency: Less manual coordination and fewer status checks 

Workspaces API use cases and sample app

To make this concrete, we built a Workspaces Sample App that demonstrates two real-world workflows: onboarding a new wealth management client and managing a hospital's care plan approval inbox. Both are available to explore today.

The sample app is written in C# and React, runs locally via Docker, and the full source is on GitHub.

Use case 1: Dynamic workspaces for event-driven workflows

Dynamic workspaces are created on demand in response to a specific trigger, such as a new user record, a submitted form, or a kicked-off process. They're well-suited for workflows that have a clear start and end, where each instance is unique.

When to use this pattern

• You need to spin up a workspace per person, deal, or transaction

• The workflow has a defined lifecycle (start, complete, close)

• Participants are external or vary across instances

How it works

1. Your application detects a trigger event (e.g., a new record is created)

2. Call the Workspaces API to create a new workspace and add the relevant participant(s)

3. Use the eSignature API to generate draft envelopes and attach them to the workspace

4. Add any document upload requests or tasks required to complete the workflow

1. Monitor workspace activity through the API as participants engage

The result: each workflow instance gets its own organized hub, and participants always know where to go and what still needs their attention.

Use case 2: Persistent workspaces for ongoing workflows

Persistent workspaces are long-lived hubs tied to a person, team, or role rather than a single event. New items are added over time as work comes in, making them a good fit for recurring or queue-based workflows.

When to use this pattern

• The same participant receives a steady stream of documents or tasks

• You want to consolidate routing across multiple upstream processes

• Participants should only be notified when something new arrives, not for every update

How it works

1. On first use, call the Workspaces API to check whether a workspace already exists for the participant; create one if not

2. As new documents or agreements are generated, add them to the existing workspace via the API

3. Docusign handles participant notification logic automatically, sending one initial notification and only emailing participants again if new tasks are added after they have already accessed the workspace.

4. Participants access one location to review, sign, or act on whatever is waiting for them

The result: instead of building a notification and routing layer yourself, the workspace becomes the inbox. Your application adds work to it; participants drain it.

Constraints and limitations to know

• The Workspaces API is currently in beta, so endpoints and behavior may change. Be sure to check the official documentation on Workspaces API rules and resource limits. 

• Workspace deletion and archival are not currently supported via the API  

• At the time of this post, complete management of documents added to a workspace was not possible solely via the API. Some actions, such as setting sharing rules, require managing users to execute via the Docusign user interface

Get started with the Workspaces Sample App

The Workspaces API (beta) makes it easier to design scalable, collaborative agreement workflows without building complex UI or relying on disconnected tools.

Whether you’re onboarding clients, managing internal approvals, or building entirely new agreement-driven experiences, Workspaces provide a flexible foundation you can extend. 

You can explore the Workspaces API in two ways:

• Try the live instance: Explore the Wealth Management and Healthcare workflows on the Docusign Developer Center sample apps page. Log in with your developer credentials to walk through both scenarios

• Inspect the code: Clone the repository opens in a new tab on GitHub, run it locally via Docker, and modify it for your own use case. The repo includes C# and React source

Additional resources

• Workspaces API reference

• eSignature API reference

• Docusign Developer Center