I want to add docusign functionality to an iOS app using this API:
https://www.docusign.com/developer-center/api-overview
Consider this use case:
An agent visits a client in their home. The agent brings his own iPad with my app installed. While interviewing the client the agent fills in all the information on the iPad app that I provide. This is a regular application; not a fillable .pdf. A fillable .pdf is not sophisticated enough to gather all the information we need to gather.
At this point the app could generate a .pdf with all the data that was gathered.
What are my options to have the client sign the document?
Is is possible for the agent to hand the iPad to the client for signing?
Can the client sign without an email address?
What are the caveats to those options?
The docusign site is good, but it is not easy to understand the user experience from the API.
I would guess that the client needs an email address and needs to sign the forms on their device that receives email, but I wanted to confirm.
Take a look at Docusign embedded signing for your usecase.
Embedded Signing - or the Recipient View workflow - allows users to
sign directly through your app or website. When you embed your
recipients you are telling the DocuSign platform your app will
generate signing URLs, authenticate your recipients, present the
signing request, and re-direct once the transaction is complete.
For browser integrations re-directing or framing can be used to host
the signing workflow, for mobile apps (iOS and Android) you should use
a webview.
Related
I have an app were there are 2 kinds of users.
A builder and an owner.
Now there is a centralized platform that I am building, were each builder who have their own docu sign account with them, will register. And then provide with a docusign URL (I am not sure what that is), and the owner then clicks on the link, once they are logged in to their part of the system. They sign the document using docusign and the builder gets the corresponding response in the centralized system.
Is this approach can be done using docusign? Or the working of this is completely different?
You're likely referring to embedded signing vs remote signing from what I understood from your description.
https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/
In embedded signing, your app will take care of authenticating the users on DocuSign's behalf.
Yes. The Builders are the DocuSign senders. As you say, they have the DocuSign accounts that will be integrated into your system.
The owners are DocuSign recipients. More specifically Signer Recipients.
The owners do not sign into DocuSign at all. They may register (and login) themselves with your app, that's a different issue.
When appropriate, the owners click a link on your app to sign documents.
You then have some options: did the builder initiate a signing request for the owner to sign at some point in the future? Or is the signing request initiated when the owner decides that they want a document generated that they will then sign? (Or both?)
When it comes time for signing, if the signing ceremony is presented by your app to the owner, we call that embedded signing.
If the builder initiates a document to be signed by the owner, then the quickest technique is to immediately send a signing request (by email or SMS) directly to the owner. That's called remote signing by DocuSign. (The other way to do it is to wait until the next time the owner logs into your app. I would not recommend this since it would tend to slow down the completion of the signing process.)
I am developing one application and successfully integrated it with DocuSign.
I am sending an envelope to the user using docusign API, the email sent from docusign host, when the user clicks the email it navigates to DocuSign website. Is it possible to edit the email sent link and sign from my own website?
Note: Still ok, if this functionality available any other third party instead of DocuSign.
Yes, please have a look at our embedded signing page:
https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/
More specifically, review createRecipient API: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createrecipient/
Let us know if you still run into issues implementing this.
I am new to Docusign and we have a requirement to integrate Docusign in our web app. I have gone through all the links for integrating docusign into a web app using REST Api calls. After thorough read and watching youtube videos, I came to know that we can integrate docusign in our web app through REST API calls but for the same additionally we need to develop our own UI to upload documents and send it to the recipient. But basically we are looking something where we can be reidrected to docusign from our webapp to perform all the operations of sending document for signing and once document is sent then I will be redirected back to our web app.
Kindly help with the above query and let me know if my understanding is correct for integration of docusign and for the same developing our own UI in our web app. Also please let me know if there is any alternative to fullfill the requirement of directly accessing docusign from our web app and performing all required operations of sending a document to recipient.
Thanks in advance!
So you want a button on your web app that says "Sign with DocuSign" and then what?
Most customers who want to send from their web app already have the documents controlled by their web app.
They:
authenticate the user with DocuSign (OAuth Authorization Code Grant)
Upload the document to DocuSign from their app.
Add tabs (signing fields) to the documents programmatically. (This is not hard and it saves the sender a lot of work.)
Upload the recipients (signers, copy-only recipients, etc)
And then tell DocuSign to send the envelope (the transaction).
Applications can also monitor the progress of the envelope through the signing process and programatically act on the signed documents.
The above is not hard to do and provides a good user experience.
You can also redirect the user of your application to DocuSign to accomplish any/all of the above manually. But the more the user does manually, the less convenient the integration will be for them.
If you want the manual experience, check out the EnvelopeViews::createSender method.
I want to add the docusign API with my application I create the docusign development account. I dont want to go mail to the signer. Its work automatically when my a user enter in my website and click to button go to docosign application. How i can do that. any one can help me?
Marco is right that you need to be careful about how you authenticate users who are coming into your application. The proof that the signature took place is only as strong as your authentication system. DocuSign has over 7 security options and the e-mail activation gives it more validity.
Having said all that you can absolutely embed DocuSign into your application. Here is a walkthrough on how you can embed DocuSign into your web application: https://www.docusign.com/developer-center/quick-start/embedded-signing
You cannot have a link in your application because this would reduce the value of the electronic signature: it would be more difficult to proof that the real signatory signed the document if the link was accessible not only to the recipient of the email.
DocuSign wants to be sure that their servers are the only one who manage the links for signatories.
There is no API to get the link.
We currently use the API for embedded signing in our web application. When reviewing doc reference guide for offline signing, I'd say it's less than crystal clear how that really works. If I'm offline when I obviously can't call the API, so how does one in fact "sign" with DS?
I can appreciate how our client app (again, which currently does embedded signing) can prepare an envelope 'request' offline, and then send that request once we have connectivity. However the REST API guide says the user in fact "signs" the doc while offline -- how does the user ever get to the Docusign interface to do signing?
from the docs
To use Offline Signing, the customer using a client application to
create an envelope on an Internet-capable device, such as a smart
phone or tablet, that is not connected to the Internet and has a
recipient fill out and sign (or initial) the envelope documents. When
the device later connects to the Internet, the client application
uploads the envelope information to DocuSign where it is processed.
Does our offline app (running, say, in/as a Chrome app) somehow connect to local client Docusign software onboard the laptop or mobile device while offline? Any pointers to more complete documentation?
From the docs:
"IMPORTANT: Access to the offline signing capability is limited by
integrator key information. If your integrator key does not have the
correct authorization, you cannot use offline signing. Access to the
offline signing capability will be evaluated on a case-by-case basis."
The reason is because your software would be responsible for providing the legal evidence that the transaction actually happened with the proper security checks. This requires a tighter business arrangement and agreement between your company and DocuSign.
Please get in touch with your business development manager and they can set up a time to talk.
-mb