In DocuSign connect, I've configured it such that when a user has completed signing the documents that were emailed to them, DocuSign will send an HTTP POST request that includes the signed documents to an endpoint on an app on our servers that I've specified.
For the purpose of managing whitelists and firewalls, members of my team are asking what URL the request is going to come from. I haven't found a straightforward answer in the documentation. What URL does the request come from?
Thanks for reading.
The URL cannot be fixed and more URLs can be added in the future.
If you can use wildcards for something like *.docusign.net *.docusign.com then you should be good.
You can whitelist specific DocuSign IP ranges defined for any of our sites. See the list on this page
Related
So far i finished Docusing integration with our DMS including webhook listener, when we config for Custom Connect, url to publish not supporting http://, in some articles mentioned it support htpp and https, in some article not mention http will support,
I have demo sandbox account in Docusing, from my account setting page, if i enter url to publish link for webhook listener and i click save button, it will not save, it show error like "url need https"
Screenshot -http://prntscr.com/v3n6en
Pls advise me what i did wrongly ?
Regards,
Aravind
Unfortunately you can't use HTTP with Connect
This guide explains it
Quote from Q&A:
DocuSign Connect is used to transmit sensitive data about your envelopes across the Internet. As part of DocuSign’s focus on security, we are upgrading all notifications to use HTTPS only.
Hope this answer your question
I am trying to push notifications from DocuSign Connect to our webhook.
Is there any way to provide a header named Appkey and a given value when DocuSign connect pushes notifications to the provided webhook URL?
Our webhook requires a header named AppKey to access it.
Currently, I don't see any such configuration in Docusign Connect UI.
Drew is correct that custom headers can't be supplied at this time.
A possible workaround: you can supply parameters via the URL's query parameters. Eg use URL https://docusign-listener.example.com/?appkey=123
Remember that, thanks to the SSL/TLS protocol, the query parameters are NOT visible to anyone tapping the line since they are only sent after the encrypted channel is set up between the client (DocuSign) and the server (your app).
Also, if you'd like to be able to specify headers for the notification message requests, ask your DocuSign technical contact to add your organization's information to the internal ticket CONNECT-1109. Adding your information will help increase the priority of the enhancement request.
No, DocuSign Connect doesn't support custom headers.
I created application and using e-signature using Docusign.
I want to get Envelop status updates using Docusign Webhook through eventNotification.
I hosted my website into public accessible environment also enabled ssl here is
my webhook url - https://103.231.46.2:10167/api/webhook
As per the Docusign feature, when Envelop status gets changed then webhook try to post some data into webhook url but it's getting failed and I can see that failed post request at Docusign -> connect -> failure tab. here is screen shot enter image description here
I have check with with my network team, No firewall is blocking. and also tried to post some data using fiddler from other network it is working fine. then I am wondering, why Docusign webhook is unable to post data into my webhook url.
I am unable to access the URL https://103.231.46.2:10167/api/webhook
Looks like it is not publicly accessible.
Use a tool like GeoPeeker and make sure your URL is indeed publicly accessible.
As CodingDawg suggested, it should either be publicly accessible or becasue of security concern you don't want it to be publicly accessible then you have to work with your Network/Firewall team to whitelist DocuSign IPs. You can find DocuSign IPs at
https://trust.docusign.com/en-us/trust-certifications/whitelist/
In my testing, I used a web proxy to get thru the firewall here so I could send envelopes. Now I will no longer be using the proxy. Do I need to log in for each web request ( like getting the templates, creating an envelope, etc )? The way we will use docusign is like this: a client consultant will see 3 documents that need to be sent to user X. So they will create an envelope with the 3 documents and send it out. They only need to connect to Docusign for a few rest calls and then they're done. The client consultants will connect to Docusign a few times a day, maybe no times a day if there are no documents to send. I'm assuming that I should go out and see if I can connect to Docusign without a problem before attempting to send out an envelope. What workflow are other people using in similar situations? Thanks for any advice.
I think a short answer here is that every API call you make requires a form of authentication provided, whether it is username/password or an oauth token passed in the appropriate x-header in your API request. I doubt your proxy was adding this on your behalf, so IMO I do not see what you will be gaining/losing by removing the proxy.
I have a requirement where I have to count all sent email by users belonging to a domain that they manage with google. All email is of course managed with gmail.
Although this task initialy seemed trivial, there doesn't seem to be a way to do this directly, meaning through some API call.
Any ideas?
Thanks
Stelios
As far as I know the Gmail API doesn't offer access to the total of send items.
Tthe g4j project (written in Java) reverse engineered Gmail's protocol in order to access an account using HTTP calls. However, the solution is fragile since it could be easily broken whenever Gmail decides to change its HTTP protocol.
Screenshot of a Java application build on top of g4j:
It's not easy but there is a way to access a gmail account.