Question??? My company is using docusign for esignatures and we have run into a situation were we need to have the signed copies of the documents without the copy view watermark on them. To remove them we have turned to a site called eoriginal which will clean up the docs and remove the cope view watermark, however we are continuing to have numerous issues with this service. So I am attempting to find an alternative solution, any feedback or suggestions are much appreciated.
Not knowing what your issues are, I'm not sure I can help, but have you looked at our dev center article about how to export authoritative copy using the DocuSign eSignature SOAP API? It covers this topic in details and explains that you can do this given the following prerequisits:
You must use the SOAP API
Your account must have access to the
Authoritative Copy feature. Contact DocuSign Customer Support and ask
that your API user be granted permission to export Authoritative
Copies.
If you want to select which envelopes will record an
Authoritative Copy, add "authoritativeCopy": "true" to the envelope
definition in your API call.
If you want all envelopes to use
Authoritative Copy, ask DocuSign Customer Support to set the "Auto
Authoritative Copy:" to Enabled on your account.
Finally, it's important to note this is a one-time action, and once it is done - you can never do it again (for a given envelope).
Related
First of all, I apologize for eventual noob questions, we are very new to the DocuSign API and are currently trying to wrap our heads around which is the most correct way of accessing the API.
I will start with an overview of our use case. We recently purchased a DocuSign prod. Account with an Organization enabled.
We have a Partner which uses a CMS Tooling which integrates with said DocuSign Account. This Tool allows for the Backoffice to create envelopes with documents inside and a url which leads to the signin ceremony through the Templates that we create inside the DocuSign Account. This url is afterwards send to the customer for them to sign the documents in the envelope. This Part is working and is currently being used.
Now what we want to achieve on our side, we have a nextJS web-app which allows the same customers (Which are the receivers of the created envelopes in the step above, same e-mail in both steps) to sign-in our web-app. We want to show the customer in a dashboard, if there are envelopes for him open that he can sign and if this is the case we want to show him the url which leads to the signin ceremony.
We were able to see that as soon as an envelope for a certain User is created through the CMS Tooling, we can see that envelope in our DocuSign Prod Account.
Now our thought process was, to show our customer his open envelopes, we just fetch all open envelopes in our DocuSign Account which match the customers E-Mail.
Is there anything wrong with this process or are we overlooking something?
And if it is okay to proceed this way which of the OAuth Flows is the correct one to use for this case?
From my understanding, the JWT Flow seems like the most reasonable one? Since the Customers that need to sign the documents, will not have any DocuSign accounts.
What have you tried to solve the issue?
We tried using the direct API Access, which worked when set up correctly but since we didn't have a OAuth Flow in place the Access token is only valid for restricted amount of time obviously and has to be refreshed. Hence we have to think first about how to grant access correctly
I would love to hear, what the right approach would be to achieve our desired result.
Once again Apologies for this kind of question, just trying to have a better understanding before we start building :)
Best regards!
According to the use case you mentioned using JWT Grant is fine as users of your integration will use a single system account to log in, you should use JWT Grant.
I would recommend going with the below link to know more regards different use cases and check the knowledge
https://developers.docusign.com/platform/auth/choose/
https://developers.docusign.com/platform/auth/oauth2-requirements-migration/
I'm developing a connector between our platform and Docusign.
We need to create a Draft envelope in Docusign with a specific account and then transfer the ownership of the Draft to another account.
Looking at the documentation I've not found any clue of how we can do that, I just found how to create transfer rules but they don't fit our use case.
Envelope Transfer Rules can either happen at the point of sending, or the point of completion. While it's still a draft, an envelope cannot be transferred.
Additionally, Envelope Transfer is not currently available through the REST API, so all-or-nothing transfer rules are effectively the only option.
Envelope Custody Transfer is only currently available for accounts that are part of the same Organization and on the same server. You can see which server your account is located on by going to Settings > Apps & Keys and checking the value for your account's baseUrl. For example, if both accounts have a baseUrl of www.docusign.net, they can transfer between each other. If one is on www.docusign.net, and the other is on na2.docusign.net, you cannot transfer the envelope.
Please see the following for additional details: https://support.docusign.com/en/guides/org-admin-guide-envelope-transfer
I'm working on testing our application and have the need to simulate signing of a document via the API. These aren't real documents I just need to be able to set the signing the order in a specific order but I don't receive emails for recipients until the previous one has signed. So is it possible to use the DocuSign API to sign a "Sign Here" tab? Or do I have any other options?
I haven't been able to find any clear information on this topic although I fear the answer is not. Looking through DocuSign's REST API there's a couple of endpoints that suggests I might be able to do this but I'm not quite sure it's referencing what I'm looking to do. The following endpoint has a GET and PUT function but not sure it's what I want.
{{baseUrl}}/envelopes/{{envelopeId}}/recipients/{{recipientId}}/signature_image
No, the DocuSign API does not have a functionality for 'robo-signing'.
If the goal is to check routing order, you could change a Signer to a Carbon Copy recipient: CC roles are immediately completed.
For reference, the signature_image API calls allow you to view or change a user's adopted signatures. They shouldn't be used to apply a signature to a document.
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
A 3rd party website is offering our service to their members. When they sign up, members have to agree to our contract. Currently this is handled manually, with envelopes being sent through email. We want to streamline this process allowing members to enter their information into the web site, and then immediately be presented with a contract to review and sign.
The 3rd party web site will collect the member information, then use the REST API to create a draft envelope based on a Template and information the the member enters on the website. The application will then display the contract in the web page so that the user can review and sign it. The document workflow will ensure that signed copies are routed to appropriate parties within our company via email for completion.
We want the 3rd party web site to have access to an account to which we can share templates. We want the 3rd party application to have very limited capabilities trhough the API:
Submit requests using a User ID and Integrator Key that we provide. These credentials need be different from other User Ids and Integrator Keys under our account
Create a draft envelope based on the templates we provide
Post a Recipient View allowing the application to display the document for review and siganture (in an IFrame)
Receive the signing status via the return URL provided in the Recipient View post
Possibly request status for an envelope
The external application should not have access to other templates, documents, or unnecessry API calls.
We want to be able to cancel the application's access at any time.
Question: Permissions and API Limitations
Is the above scenario feasible with respect to establishing limited access to the DocuSign REST API? How would we set this up?
Do account user permissions limit API use, if the API is enabled for the user? I found these settings in the user permissions section of the documentation. I can make guesses as to how to set them, but I need guidance on the actual implications of some settings.
Submit DocuSign API Requests: true
Manage Account: false
Send Envelope: true
Manage Templates: Use
DocuSign Desktop Client: false
Transfer Envelopes to User: false
Allow sender to set email language for recipients: false
I assume "Account-Wide Rights" should be false, but under that option in the documentation, it lists RequestStatus as one of calls covered. Will an application embedding the signing process still have sufficient permissions to complete the tasks listed above if "Account-Wide Rights" is false?
Are there other settings or issues I need to consider?
Firstly, thanks for using DocuSign. The answer to your question is in a few different parts. To clarify, I am answering assuming:
1.) You are a current customer (or about to be one) of DocuSign.
2.) You have a plan that is set up to allow integration (IE you aren't trying to do all of this with a personal plan, or something like that).
There are a couple of terms I will use... Sender and Recipient. In this scenario, the THird Party Website is "the sender" and they are Sending the documents through YOUR DocuSign account, using the API. The people who are signing up for your service are going to be Envelope Recipients.
Just like with the post office, someone has to send, and someone gets the envelope.
So far so good.
So what will happen is that the third party website will write some code that knows how to talk to the DocuSign API, and you will need to know:
-DocuSIgn Account ID (this is your DocuSign account)
-The Integrator Key (this is the key that you will need to certify before going live, which identifies all those API calls as coming from them)
-Credentials to access your account (this can be either the actual creds, or a token, etc).
Now, there are two ways to do it. You can either have the third party website make the and send all of the envelopes as if they all came from a single "user" in DocuSign (likely) or if you know that a particular user should send out things, you can do that too.
I am going to assume that all of the sign up packets will be sent as if they came from something like Signup#company.com.
So you will make sure you have a user in your DocuSIgn account with that Email address and name, and make sure that user has the ability to send via the API (there's a setting in DocuSign admin), and all envelopes will be sent as if that "person" sent them.
You will need the settings for that user (the one that will "send" all the envelopes), set as you showed above. You would need the Account Wide access if you wanted to send "on behalf of" a different user. But you aren't doing that, so you should be cool.
The last thing is that you will need to make sure you have an envelope based plan (as opposed to a seat based plan) because otherwise, that one mega-user will look suspicious (sending hundreds of envelopes in an automated fashion).
I hope this answers the question?
-Dan