Currently I am using #DocuSignAPI to create envelope in which API required x and y position to add signature from recipients.
So my requirement is like if i upload the document it should be redirect to the Docusign UI where recipient would login and sign the document.
So the thing is instead of creating rest call via API.
I need some api where Docusign is going to handle by its way so i do not need to create UI for that which is very complex to build from my side.
Anyone can help me with is will be really great.
Thanks in advance
Check out this DocuSign recipe: Sign from Your App.
This sample (and many others) are available on the DocuSign Developer Center, along with tons of documentation about various integration scenarios and API reference.
Related
This is my first time posting so apologies if I don't explain things clearly.
I've created a Custom Connector within Power Apps that does an API call to my DocuSign Account. The API call I am currently leveraging is to create DocuSign Envelopes:
/restapi/v2.1/accounts/{accountId}/envelopes
Link to DocuSign API Library: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/create/?explorer=true
My issue is that I do not know how create Envelopes on behalf of other DocuSign Users while using the API call within my Connector. Since the Custom Connector required me to log into my DocuSign Account, every time I use the Connector the Envelope generated from the API call gets associated to me (I am able to see it within "Drafts" when I log into my DocuSign).
Sorry if this is a bit confusing. My end goal is to use my Custom Connector and its API calls within a Canvas App. However, I want the Envelopes created not to always be associated to my DocuSign account especially if the Canvas App is used by other End Users.
Any help would be much appreciated!
Thanks!
Screenshot of Test call:
Request
Screenshot of Test Call: Response
Screenshot of Envelope within DocuSign Account: Snippet
This is Yara from DocuSign Developer Support.
Since you want to create envelopes on behalf of other DocuSign Users while still using the API call within your connector, you can use the Send On Behalf Of Functionality (SOBO). This functionality allows a single user in an account to authenticate for other members of the account and send fully defined envelopes on their behalf.
Here's a detailed guide on the SOBO functionality: https://developers.docusign.com/docs/esign-soap-api/esign101/auth/send-on-behalf-of/
Right now I can't find a way to have the user to sign the document using DocuSign in our own application. What I need to do:
Have the user sign the document in our own application.
Get the signature with an API from DocuSign
Any help will be so much appreciated.
Yes, this is called "embedded signing" and is one of the most popular use-cases with the DocuSign eSign API.
Here is the Node.js code example to do this:
https://github.com/docusign/code-examples-node/blob/master/lib/eSignature/examples/embeddedSigning.js
I need to integrate docusign into our portal.Our users will come to our portal and
then upload documents and using DocuSign API we need to sign docs. I was able to
get it working embedded. Now the problem is the placement of signing controls
(Where the signature should appear in the docs)
Can I upload the documents to DocuSign portal straight and then using API
sign it from my portal? The idea is that the envelope creator can place all
the signature using the nice interface in DocuSign...Would this be possible?
Or is there a way I can integrate the placement of signing controls part
on my portal using DocuSign?
Any thoughts would be greatly appreciated.
thanks
Yes, you can do that.
Check out this code example on the DocuSign Developer Center:
https://developers.docusign.com/esign-rest-api/code-examples/code-example-embedded-sending
If you told me which code lang you use - I can put some code in here too.
I'm trying to achieve some requirements via Docusign APIs. Would like to know if it's possible before I start the project.
I've used Docusign app for Salesforce earlier, but now I'm trying to achieve some functionalities through API calls
Ability for a Signed Document sent to a contact (by clicking on a button on contact record) to be attached to the Contact record it was sent from
Ability to write back to the record from a field tagged on the DocuSign envelope
Vinay, this functionality is available using the DocuSign for Salesforce integration. If you would like to write it yourself using APIs, you can start by looking at our Apex toolkit here - https://developers.docusign.com/salesforce/guides/apex-toolkit
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.