How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Docusign EnvelopeViews API

Generate URL tokens for embedded signing, sending, and recipient views to integrate DocuSign experiences directly into your application.

Docusign EnvelopeViews API is one of 134 APIs that Docusign publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 1 JSON Schema definition.

Tagged areas include EnvelopeViews. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, a JSON-LD context, a getting-started guide, rate-limit docs, and 1 JSON Schema.

This API exposes 9 operations across 8 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 5 base URLs: https://demo.docusign.net/restapi/v2.1, https://www.docusign.net/restapi/v2.1, https://eu.docusign.net/restapi/v2.1, https://au.docusign.net/restapi/v2.1, https://www.docusign.net/restapi.

9 operations 8 paths 10 schemas 1 DELETE8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://demo.docusign.net/restapi
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Docusign EnvelopeViews API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode and implicit flows, exposing 3 scopes.

  • OAuth2 — DocuSign uses OAuth 2.0. Supports Authorization Code Grant for user-present applications and JWT Grant for service integrations.

Paths & Operations 9

Across 8 paths, the API surfaces 9 operations — 1 DELETE, 8 POST. Each is listed below with its method, path, parameters, and response codes.

EnvelopeViews 9

Generate URL tokens for embedded signing, sending, and recipient views to integrate DocuSign experiences directly into your application.

POST
/accounts/{accountId}/envelopes/{envelopeId}/views/recipient
Docusign Create an Embedded Recipient Signing View
EnvelopeViews_CreateRecipientView 2 params body → 201400401404
POST
/accounts/{accountId}/envelopes/{envelopeId}/views/sender
Docusign Create an Embedded Sender View
EnvelopeViews_CreateSenderView 2 params body → 201400401404
POST
/v2/accounts/{accountId}/envelopes/{envelopeId}/views/correct
Docusign Returns a URL to the envelope correction UI.
Views_PostEnvelopeCorrectView 2 params body → 201400
DELETE
/v2/accounts/{accountId}/envelopes/{envelopeId}/views/correct
Views_DeleteEnvelopeCorrectView 2 params body → 200400
POST
/v2/accounts/{accountId}/envelopes/{envelopeId}/views/edit
Docusign Returns a URL to the edit view UI.
Views_PostEnvelopeEditView 2 params body → 201400
POST
/v2/accounts/{accountId}/envelopes/{envelopeId}/views/recipient
Docusign Returns a URL to the recipient view UI.
Views_PostEnvelopeRecipientView 2 params body → 201400
POST
/v2/accounts/{accountId}/envelopes/{envelopeId}/views/sender
Docusign Returns a URL to the sender view UI.
Views_PostEnvelopeSenderView 2 params body → 201400
POST
/v2/accounts/{accountId}/envelopes/{envelopeId}/views/shared
Views_PostEnvelopeRecipientSharedView 2 params body → 201400
POST
/v2/accounts/{accountId}/views/console
Docusign Returns a URL to the authentication view UI.
Views_PostAccountConsoleView 1 param body → 201400

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are recipientViewRequest (16 properties), RecipientViewRequest (11 properties), correctViewRequest (3 properties), consoleViewRequest (2 properties). Each schema is shown below with its type and property counts.

ErrorDetails
object
Contains error information returned by the API.
2 properties
ViewUrl
object
Contains a URL for an embedded view.
1 property
RecipientViewRequest
object
Request body for generating an embedded recipient signing URL.
11 properties 4 required
errorDetails
object
This object describes errors that occur. It is only valid for responses, and ignored in requests.
2 properties
consoleViewRequest
object
2 properties
recipientViewRequest
object
16 properties
correctViewRequest
object
3 properties
EnvelopeViews
object
Embedding Envelope views
1 property
viewUrl
object
1 property
returnUrlRequest
object
The request body for the EnvelopeViews: createSender method.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

docusign-envelopeviews-api-openapi.yml Raw ↑

Other APIs Docusign publishes across the network.

Docusign Web Forms API
Docusign Notary API
Docusign Navigator API
Docusign Workspaces API
Docusign CLM API
Docusign Connected Fields API
Docusign AccountBrands API
Docusign AccountConsumerDisclosures API
Docusign AccountCustomFields API
Docusign AccountPasswordRules API
Docusign AccountPermissionProfiles API
Docusign Accounts API
Where this information came from

This is an independent, third-party profile of Docusign EnvelopeViews API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.