Can we import many documents from DocuSign through the API? - docusignapi

A customer of ours likes using DocuSign's bulk send feature to get a lot of employees to sign documents.
They want the ability to then import these signed documents into our software. We're thinking of creating a GUI in our software that lets them browse the folders in DocuSign, select which envelopes to import and then import them.
A user may want to import 50 envelopes at a time. In this case it would make a few API calls when the user is browsing through their folder, then it will make 50 calls to RequestDocumentPDFsEx to download the documents associated with each envelope. The API calls would probably be done serially unless they're really slow. In that case we may have to use 2 threads or more so that it completes in a decent amount of time.
We only have one customer at this time that is looking at using this feature and it would not be used very often, maybe once a month.
Will we run into a problem with rate limiting or breach any terms if we implement the above described solution?
We already have a certified integrator key for our integration that allows users to upload a handful documents at a time to be signed.

I think you're only options here are:
DocuSign Retrieve - a separate, paid module that DocuSign offers used for bulk downloading
One API call per envelope download
DocuSign Retrieve - "Download envelopes, documents and data from DocuSign for use with external systems. DocuSign Retrieve runs on your system as a one-time request or on a recurring basis. Configure DocuSign Retrieve to specify file type and storage location."
Otherwise as you have suggested you'll need to make one API call per envelope download, either through the SOAP API or through the REST API.

Related

How to sign a document via api call?

How can I sign a document via API call without email client and UI interaction? Or if there is no way to sign, perhaps there is a way to force change status of a document?
I've seen many people asked for this and the answer was no, but all those posts are 2 years old. Perhaps there is a solution to it today?
It is possible to do everything via UI, but it is a terrible idea to spend time on an external service instead of your system under test.
Some say it defeats the purpose as the signer must view the document first, yes, but it is irrelevant, I simply want to test the flow of the system under test.
Please advise!
For testing purposes, you do not need to unit test the DocuSign signing ceremony since we test it all of the time. Instead, test that your API calls create the DocuSign envelope correctly.
For example, after your application creates the DocuSign envelope, your tests can interrogate DocuSign (via the API) that the envelope exists, is ready to be signed, etc.
If you're using embedded signing, you can test that your app can successfully obtain the URL for the signing via the DocuSign API.
For an end to end test, test software is available (from test software organizations) to interact with a web browser as a human does. Only test envelopes can be "signed" in this way.
For production signing of documents, the DocuSign signature appliance supports programmatic signing of documents using standards-based signatures (digital signatures). Your workflow must be authorized to sign documents on behalf of the signer.
For example, programmatically signing invoices sent by a company to its customers.

Does docusign webhooks notify about template changes

Use Case -
We are an origanization who helps universities manage the sport activities and contract of their students. We are planning to integrate docusign in our system both web and mobile app. One feature that we need is the information regarding the created templates, is there a way to get notified about templates via webhooks(like when it was last used, or created).
So, webhooks may not be suitable to know when a new template is created, because currently the webhook is tied to an existing object, and the object is not yet there, so it's a catch22.
What you can use instead is the DocuSign Monitor API. It's a different approach, but using this API, you can get data about anything that happens in the DocuSign account, including templates.
You can make raw API calls, or use the Monitor SDKs for one of six languages.
I'm not 100% on this but one approach would be to use folders. Put your templates in a named folder and use the listStatusChanges API with a folder id as a query parameter (https://developers.docusign.com/docs/esign-rest-api/how-to/list-envelope-status-changes/)
You can also select "Folders" in the "Include Data:" section of your DocuSign Connect webhook and filter for the folder(s) you're looking for.

DocuSign Bulk Send w/ CSV User Portal

The current goal is to be able to send multiple files to multiple recipients through the user portal on our website. We want to make this process as efficient as possible because we will have lots of files to sign. Lastly, I would need a way to track and save all the users.
From what I know about docusign, I am able to send a file to multiple recipients in bulk using bulk send using just the website and not having to use the API at all. Is it possible to send multiple files to multiple recipients through the same CSV? Or would it be better to just send each file separately to multiple clients and do that for each file? Also, I'm wondering if it's possible to do that in the API as well. Previously, I achieved sorting clients ID & envelope ID using the docusign api with PHP and connected it to a database. Let me know which method seems optimal for my solution.
Steven, you can use the API to use Bulk Send.
In fact, with the DocuSign eSignature API v2.1 this functionality is much improved and allows you to do all of the above.
See here for more details: https://www.docusign.com/blog/dsdev-deep-dive-discussions-bulk-send-with-esignature-api-v2-1/

eOriginal/eVault integration with DocuSign

My company recently signed up for partnership with DocuSign to build your
signing routine into our software.
The client looking to use our software currently uses DocuSign to sign
documents and has an integration with eOriginal as the eVault for the
documents.
Based on the documentation I'm reading, when the document is sent to
eOriginal, it is removed from DocuSign.
Is that correct? My client vaguely agreed that it wasn't on DocuSign but
I'd like to verify this.
We have our own document storage system as well and while we would like
eOriginal to have the authoritative copy of the document, we'd like a copy
of the document to be stored in our solution.
Our initial thought was that after the document was signed, we would
download a copy through your API and store it on our system.
We now wonder if that document would be there.
How soon after a document is signed would be it be pushed to eOriginal?
If there isn't enough guaranteed time to pull the document down, we'd need
to possibly pull it from eOriginal instead.
If we are pulling it from eOriginal, is there any information on how that
would be identified in eOriginal.
I'm not asking for their API. I get that we most likely need to get in
contact with them but is it identified by the same envelopeID?
Please let us know any insight you can provide on this.
We appreciate your assistance
The Setup
The configuration you're using all depends on your account settings. Please contact your DocuSign Account Manager to get a better explanation of the options and pricing here.
The most commonly used combination that I see with DocuSign/eOriginal is:
DocuSign Transfers Authoritative Copy to eOriginal
eOriginal stores the Authoritative Copy
DocuSign stores a copy
As far as timing goes, the event happens when the envelope has been fully completed. It could be anywhere from less than a second up to 15 minutes, depending on how DocuSign and eOrigional's queue's look. It's normally closer to the "instant" side. But I would plan for latency between the two systems.
How eOriginal Stores Envelopes from DocuSign:
eOriginal uses EmailSubject of your Envelope for the Containter ID.
There is an additional eOriginal Custom Field Xref1 which contains your DocuSign EnvelopeId

Getting Merged documents using CONNECT API

Currently I am using CONNECT API configured with my system.
Whenever DocuSign Envelope moves to Completed status, a POST request is generated to my system which contains:
DocuSign Envelope information
DocuSign PDF bytes ( Seperate PDF documents )
DocuSign certificate
I selected the option [X] Include Documents in Connect API and I am able to receive the PDF bytes.
Currently I am using PDFTK to merge all the documents into one.
But is there a way using Connect API to get all the Documents merged together as a one Single PDF document ?
Parallely while reading through the DocuSign REST API guide I came across /envelope/id?merge=true which would give me the required single PDF. But while digging deeper I came to know there is a concept called Integrator Key for each implementation, which would require a DocuSign Certification.
Inorder to just get a merged document instead of seperate PDF documents should I go through this certification process or is there a simple way to do the same ?
If Certification is Mandatory then what kind of certification would this fall in, because I have no front end application for signing process and I am just consuming the customer generated documents.
Using DocuSign Connect does not require an IntegratorKey or that you go through the DocuSign API Certification process. The Certification Process (https://www.docusign.com/developer-center/go-live/certification) and Integrator Key exist to ensure that DocuSign customers who utilize either the REST API or the SOAP API are not doing anything that could be harmful to the overall DocuSign service -- this is not relevant to DocuSign Connect, since Connect is merely pushing data to your listener when Envelope events occur (i.e., you're not explicitly polling DocuSign for changes, as you might with either the REST API or SOAP API).
I don't believe it's possible to configure Connect such that documents are sent merged together as one file; they're always going to be sent as separate files in the Connect message. It would be feasible to, during your processing of the Connect XML message, make a REST API call to DocuSign to request the Envelope's documents in a single file -- however, doing so would require that you use an Integrator Key, and that you go through the DocuSign API Certification process -- probably not worth the time, expense, and trouble, if there's another way for you to merge the files yourself.

Resources