Reference · built on requestConnectorCRM & sales

Docusign eSignature

Envelopes, recipients, documents, and signing events from Docusign eSignature through its REST API v2.1 and Connect webhooks.

Request accessPricing ↗

About

Docusign eSignature is an electronic signature service. Work is organised in envelopes: each holds one or more documents, the sender, the recipients with their tabs, and status that tracks delivery and signature. Envelopes are created and sent through the eSignature REST API v2.1, and Docusign Connect posts each event, such as sent, recipient-completed, or voided, to a listener you run on the public internet.

Through Fibric, an operator reads status for envelopes and recipients next to the agreement each belongs to, then proposes what comes next: send a draft, resend to a recipient who has not acted, or void with a reason. You approve or decline. The connector calls the eSignature API once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Docusign eSignature and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Status and search results for envelopes through Envelopes:listStatusChanges, filtered by from_date, status, envelope_ids, or transaction_ids
  • Recipient status and current routing order through EnvelopeRecipients:list, including tab values
  • Connect events for envelopes in JSON SIM format, named for the status reported: sent, delivered, completed, declined, voided, corrected, resent
  • Connect recipient events such as recipient-sent, recipient-delivered, recipient-completed, recipient-declined, and recipient-reassign
  • Template events template-created, template-modified, and template-deleted, and the template list through Templates:list
  • Audit events through the audit_events endpoint, and completed documents or the certificate of completion through EnvelopeDocuments:get

Proposed actions

  • Target capability: propose creating and sending envelopes from documents or a template through Envelopes:create
  • Target capability: propose sending a draft by setting status to sent through Envelopes:update
  • Target capability: propose voiding an in-process transaction with a voidedReason through Envelopes:update
  • Target capability: propose resending to a recipient, or correcting a recipient email, through EnvelopeRecipients:update with resend_envelope
  • Target capability: propose an embedded signing URL through EnvelopeViews:createRecipient for envelopes in sent status

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Chase a contract nobody has signed

    Connect reports a sent event with no recipient-completed inside the window you set. The operator proposes a resend to the current recipient, with the message, for your approval.

    With Quote Follow-up, Abandoned Quote

  • Book the order once the agreement completes

    On the completed event, the operator matches the transaction to the quote or opportunity and proposes the order in your commerce or ERP system, attaching the completed PDF.

    With Quote to Order, Deal Handoff

  • Keep a signed record for audits

    For each completed transaction, the operator files the combined PDF, the certificate of completion, and the audit events with the record they support.

    With Compliance Evidence, Audit Trail

  • Void before the wrong version is signed

    When a price list or contract template changes, the operator finds in-process envelopes built from the old template and proposes voiding each with a reason.

    With Price List Drift, Contract Lapse

Requirements

  • A Docusign developer account and an integration key; production use goes through Docusign's Go-Live review
  • The signature scope granted at authentication for eSignature REST API calls
  • Connect enabled on the account and a custom Connect configuration created by an account administrator
  • A webhook listener reachable on the public internet over HTTPS, with an HMAC key added to the Connect configuration
Authentication
OAuth 2.0 with the signature scope: Authorization Code Grant when a user is present, or JWT Grant for a service integration without a user session.

Limits

  • Accounts start with 3,000 API calls per hour, reported in the X-RateLimit-Limit header; a 30-second burst limit of 500 calls applies to production accounts.
  • Polling status is limited to once per 15 minutes for each of your envelopes; Docusign says to use Connect instead.
  • Envelopes:listStatusChanges returns at most 1,000 envelopes per call, and an account holds at most 20 Connect configurations.
  • Each of your envelopes allows 100 recipients, 32 MB per document upload through the API, and 200 MB in total.

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Docusign eSignature ↗

Questions and answers

Does the connector poll Docusign for signing status?
No. Docusign limits status polling to once per 15 minutes for each of your envelopes and flags integrations that exceed it. The connector subscribes through Docusign Connect, which posts events for envelopes and recipients to a listener and does not count against API request limits.
How are Connect messages checked?
Connect can sign each message with an HMAC key from your configuration. The listener computes a SHA256 HMAC of the request body, base64-encodes it, and compares it with the x-docusign-signature-1 header. Failed deliveries are retried with exponential backoff, then once a day for 15 days.
Which OAuth grant does a server-side integration use?
JWT Grant. It does not need a user present and suits an integration with one service login. Authorization Code Grant needs a user at the start and returns a refresh token. Either grant returns the same access token; the request must include the signature scope.
Ask about Docusign eSignature

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Docusign eSignature through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy