Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

General Description

Digital Signature(DS) API purpose to facilitate using DocuSign API for signing and delivering PDF documents.

Authentication and authorization

Only authorized users or applications can use this API.

There are two scopes of authorization:

  1. DigitalSignature.Sign

  2. DigitalSignature.Admin

User in first scope can perform all actions, except managing DocuSign users.

You should have Admin scope otherwise.

First you need to get bearer token:

var token = await app.AcquireTokenForClient(new string[] {“ClientId}/.default" }).ExecuteAsync();

Where ClientId is ClientId of application which is trying to access DS API.

Then we need to add this token to HttpClient header:

_client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", token);

After this HttpClient can perform Http request to DS endpoints.

DS API has the following controllers:

  1. Documents: managing and processing documents (certificates and envelops) in DocuSign.

  2. EVE: generating QR code for links to EVE

  3. Signing: signing documents (Html. PDF, Jpg and MS Office docs) in DocuSign

  4. Users: managing DocuSign users

Versioning

Now DS API has version 1.

How to sign documents

We can sign the following documents: Html, pdf, word, excel, power pint and jpeg. In either way we get signed PDF from DocuSign.

There are 3 ways to sign document:

  1. Embedded

  2. Email Request

  3. Template

Documents

Get current environment

/api/v1/Documents/CurrentEnvironment/

This GET endpoint allows you to download PDF document, proving EnvelopeID and DocumentID:

/api/v1/Documents/Document/{EnvelopeID}/{DocumentID}

Get envelop by id

/api/v1/Documents/Envelop{EnvelopeID}

EVE

Singing

Users

References

  1. DocuSign

  2. DS API (NCD Environment)

  3. DS API (NCA Environment)

  • No labels