DocuSign connector icon

DocuSign Connector

Embed DocuSign eSignature workflows inside your SaaS product to send envelopes, apply templates, collect signatures and surface real-time status updates for each customer account.

01

Automate signature workflows

Create and send envelopes from app templates automatically.

02

Real-time status sync

Use Connect webhooks to update envelope status instantly.

03

Governed integration actions

Expose curated DocuSign actions as managed MCP tools.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

Overview

Teams can integrate sending and managing envelopes, templates, recipients, documents and real-time status notifications from DocuSign into their apps. Using the DocuSign API you can create envelopes from templates, upload documents, request signer tabs, and receive Connect webhook events to keep your multi-tenant app synchronized.

PRODUCT USE CASES

Top Use Cases for DocuSign Integrations

Quickly build integrations that send templated contracts, track envelope status with webhooks and sync signed PDFs back to your app. Publish integrations in your embedded marketplace for self-serve activation by customer accounts.

Send templated contracts from your app

Create and send an envelope from a DocuSign template, set recipient roles and collect signatures automatically.

Sync envelope status to CRM records

Receive Connect webhook events and update envelope status and signer actions in your multi-tenant app.

Save completed signed PDFs back to user accounts

Download signed documents after completion and attach PDFs to customer records or billing workflows.

ORCHESTRATION

How DocuSign works with Cyclr

Cyclr sits between your SaaS product and DocuSign to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    DocuSign

    DocuSign processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore DocuSign methods you can orchestrate through Cyclr.

Envelopes6

Create Envelope

Action

Creates and sends an envelope or creates a draft envelope.

List New Envelopes

Action

Retrieves a list of envelopes that match your request whose status has changed since the last run.

List Envelopes

Action

Retrieves a list of envelopes that match your request.

Get Envelope

Action

Retrieves the overall status for the specified envelope.

Send Envelope

Action

Creates and sends an envelope from a template created on the Docusign website.

Create Sender

Action

Returns a URL that enables you to embed the envelope sender view of the Docusign UI.

Groups2

List Group Users

Action

Retrieves a list of users in a group.

List Groups

Action

Returns all groups for an account.

Templates1

List Templates

Action

Returns all Templates attached to account

Users2

Get User Info

Action

Returns account information and the base_uri needed to interact with the core DocuSign API service.

List Users

Action

Returns all users for the specified account

Organizations2

List Organizations

Action

Returns all Organizations

List Organizations Users

Action

Returns all users in the organization.

Connect (Webhooks)2

Connect Webhook (All Users)

Webhook

Triggers when the specified events occur for any user.

Connect Webhook (Specified Users)

Webhook

Triggers when the specified events occur for the specified users.

TECHNICAL DETAILS

DocuSign integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing DocuSign integrations in Cyclr.

API and authentication

API host
Account-specific baseUri (e.g., account-d.docusign.com, demo.docusign.net, www.docusign.net)
Authentication
OAuth 2.0 (Authorization Code); OAuth 2.0 (JWT Bearer)
Credentials

Requires integration key (client_id), client_secret or RSA private key (JWT), redirect URI and DocuSign account ID.

Method categories

Envelopes; templates; recipients; documents; accounts; users; webhooks; reporting

View vendor API documentation →

Pagination and rate limits

Pagination

Most list endpoints use startPosition and count parameters; some responses include nextUri. Pagination varies by endpoint.

Rate limits

DocuSign enforces per-account and per-IP rate limits; limits vary by plan. Handle 429 responses and backoff.

IMPLEMENTATION

Authentication at a glance

DocuSign uses OAuth 2.0: Authorization Code for user consent flows and JWT Bearer for server-to-server. Confirm which flow Cyclr enables for your instance in the Cyclr Console.

Authentication method
OAuth 2.0 (Authorization Code); OAuth 2.0 (JWT Bearer)
Credential required

Requires integration key (client_id), client_secret or RSA private key (JWT), redirect URI and DocuSign account ID.

Before you begin:

Requires a DocuSign integration key; JWT needs RSA key and user consent configured.

View setup guide

COMMON QUESTIONS

Frequently asked questions

It can send envelopes from templates, upload documents, manage recipients, and receive real-time envelope events via DocuSign Connect webhooks to sync status and signed documents.

DocuSign uses OAuth 2.0: Authorization Code for user-consent flows and JWT Bearer for server-to-server. Cyclr requires a DocuSign integration key and appropriate credentials (client_secret or RSA key).

Yes. Cyclr supports multi-tenant deployments where each customer can use their own DocuSign credentials or a central account can send on behalf of tenants, depending on your auth choice and governance.

Yes. Cyclr lets you expose vetted DocuSign actions (send envelope, create template, manage recipients) as governed MCP tools with centralized access control.