OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Docusign returns envelope status records. Search needs a date, envelope ID or transaction ID; older envelopes require an explicit date range.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Follow nextUri through envelope search results, with at most 1,000 envelopes per call.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Date, status, folder and custom-field filters select envelopes; validate returned statuses against the requested qualifier.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Access cost barrier -
-
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved.
Docusign official Node client OAuth guide ↗
OAuth implementations and code examples · Checked 2026-10-22
Downstream permission -
-
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Docusign official Node client OAuth guide ↗
OAuth implementations and code examples · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Create envelopes and send or modify drafts with the documented envelope operations.
Docusign envelope operation specification ↗
POST envelopes and PUT envelopes/{envelopeId} · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Docusign official Node client OAuth guide ↗
OAuth implementations and code examples · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
from_date and from_to_status select status changes, including deleted status. This is a bounded envelope query, not a retained CDC log.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Limit visibility -
-
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
A numeric request budget and recovery contract were not established by the reviewed references.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Status search includes changed and deleted envelope identities; purged document recovery is not established.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Overlapping date-range searches can recover matching current envelope statuses; no durable checkpoint or intermediate-event history is credited.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Docusign official Node client OAuth guide ↗
OAuth implementations and code examples · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
Docusign official eSignature OpenAPI specification ↗
GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiers · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Docusign official Node client OAuth guide ↗
OAuth implementations and code examples · Checked 2026-10-22
Rights to custom logic -
-
Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Docusign official Node client OAuth guide ↗
OAuth implementations and code examples · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
The official SDK supports OAuth authorization-code and JWT flows. Customer production activation and plan eligibility require separate confirmation.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Follow nextUri through envelope search results, with at most 1,000 envelopes per call. Date, status, folder and custom-field filters select envelopes; validate returned statuses against the requested qualifier.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| eSignature REST v2.1 envelope metadata and envelope create/update | oauth2 | Customer | Not confirmed | Not confirmed | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum plan and exact route fees remain unconfirmed.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Create envelopes and send or modify drafts with the documented envelope operations.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
from_date and from_to_status select status changes, including deleted status. This is a bounded envelope query, not a retained CDC log.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Status search includes changed and deleted envelope identities; purged document recovery is not established. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Overlapping date-range searches can recover matching current envelope statuses; no durable checkpoint or intermediate-event history is credited. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Docusign returns envelope status records. Search needs a date, envelope ID or transaction ID; older envelopes require an explicit date range. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Follow nextUri through envelope search results, with at most 1,000 envelopes per call. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Date, status, folder and custom-field filters select envelopes; validate returned statuses against the requested qualifier. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | -Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved. | Docusign official Node client OAuth guide ↗OAuth implementations and code examplesChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Create envelopes and send or modify drafts with the documented envelope operations. | Docusign envelope operation specification ↗POST envelopes and PUT envelopes/{envelopeId}Checked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Docusign official Node client OAuth guide ↗OAuth implementations and code examplesChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. from_date and from_to_status select status changes, including deleted status. This is a bounded envelope query, not a retained CDC log. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| How are integration limits disclosed? | -Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. A numeric request budget and recovery contract were not established by the reviewed references. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Docusign official Node client OAuth guide ↗OAuth implementations and code examplesChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Docusign official Node client OAuth guide ↗OAuth implementations and code examplesChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Docusign official Node client OAuth guide ↗OAuth implementations and code examplesChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedDocusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | Docusign official eSignature OpenAPI specification ↗GET /v2.1/accounts/{accountId}/envelopes: restrictions and status qualifiersChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Docusign / eSignature REST v2.1 envelope metadata and envelope create/update; OAuth applications. Document bytes, authoritative-copy transfer and full agreement-platform migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Docusign official Node client OAuth guide ↗OAuth implementations and code examplesChecked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.