developer-center | Deepin developer center , provide developer wiki | Collaboration library
kandi X-RAY | developer-center Summary
kandi X-RAY | developer-center Summary
See the wiki page to learn more information.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of developer-center
developer-center Key Features
developer-center Examples and Code Snippets
Community Discussions
Trending Discussions on developer-center
QUESTION
I'm building a java servlet page for school and I'd like to put an API inside of it. So far I've had some problems with the API.
It's the "Schiphol PublicFlight API" that I want to link to my web page.
However I can't get java to use the JSON based API.
So far I've tried to 'isolate' more and more of the JSON code, but I just can't get it to work. To make it somewhat easier for me I've separated the java servlet code from the project for now. So this is my code now:
...ANSWER
Answered 2018-Dec-26 at 06:39JSONArray ja = (JSONArray) jo.get("flights");
JsonObject flightRec = ja.getJsonObject(0);
String gate = (String) flightRec.get("gate");
//...etc
QUESTION
I'd like for all the documents created by a single DocuSign Template/PowerForm to be configured with a webhook so that I don't need to continuously poll every 15 minutes to get completed documents. I've done a lot of reading, and want to know if this is even possible in the DocuSign API.
BackgroundI have a self-service waiver document: Users navigate to a URL, fill out their contact information (i.e. define a Recipient role), and expect that their completed waiver is recognized by a linked system.
I have a DocuSign template that is being used in a PowerForm: Users navigate to the PowerForm's URL, and the PowerForm will let them create a new Envelope from the associated Template.
I'd like for the documents created by this setup to automatically notify an HTTPS endpoint upon completion, via a standard webhook.
Attempted solutionsThe Envelopes::create
method (POST /v2/accounts/{accountId}/envelopes
) accepts an eventNotification
parameter that can be used to configure webhooks. The webhook recipe covers usage of this endpoint quite nicely. This would solve my problem, if I were creating every Envelope via an API request, but I like the ease of a copy-pastable URL that comes with a PowerForm.
It's not documented, but it appears that Envelopes::update
(PUT /v2/accounts/{accountId}/envelopes/{envelopeId}
) may support configuring notifications on an already-created envelope. I could repeatedly query the most current envelopes for my template, update the notifications on in-progress envelopes and process the completed ones, but that's no better than polling.
I browsed the REST API, specifically the Templates and PowerForms categories, but I don't see any obvious way to configure either resource to set eventNotification
on created envelopes.
Here's a quick code dump of some of the API exploration I've done:
...ANSWER
Answered 2018-Jan-29 at 14:24For business reasons, Connect webhooks can only associated with all envelopes (or all envelopes from a template/powerform) if the Account-level Connect option is purchased. It is available as an add-on for many account types.
In that case, as you mention, your webhook listener will receive notifications of envelope events that it is not interested in. For those notification messages, respond 200 (received) and then discard the information.
QUESTION
I'm working with DocuSign eSignature API and following this link https://www.docusign.com/developer-center/api-overview#post-go-live
everything was going great but when I tried to get envelopeId this function didn't return anything not even error
...ANSWER
Answered 2018-Jan-17 at 17:52It's possible that the "CreateEnvelope
" returned an exception, you could add a try/catch block to see if it's the case, it might be good for your code in general in case of future errors :
QUESTION
I finally got JWT authorization working (both token access + login) using the C# SDK API. However I'm trying to figure out how SOBO works using JWT. I'm reading this help here and it shows the legacy way (username and email). I'm assuming the process is similar for JWT but I am not sure how to go about it, especially if requiring the SOBO's integrator key (for which I don't have). This help here says it is possible with JWT OAuth, but doesn't explain how. Any help would be appreciated.
...ANSWER
Answered 2017-Dec-21 at 17:23You got JWT worked by having that user's consent (either thru Auth Grant or using Admin consent). Now in legacy SOBO you used to pass SOBO user's email or userId in the Auth header, in same way while generating a token for that user using JWT you need that user's consent (if not using Admin consent) and that user's userId (sub in the JWT payload). Once you have these two important items then you can create a JWT for any user in the DocuSign. This way SOBO is replaced with more secure JWT.
QUESTION
I am new to docusign api. I am trying implement emebbed docment signing in my app using docu sign api. My requirement is need to sign two persons on single document. I have seen some examples for that, I get url for single user signing, but I didn't get the right solution. Please help me. thanks in advance
Here is my sample code
...ANSWER
Answered 2017-Dec-19 at 17:31In your code, you have
QUESTION
I want to include anchor tabs from both a server template and an inline template in a composite template document (a document uploaded at runtime). The server template contains a single recipient with the role of Signer1. The inline template contains a different recipient with the role of Signer2. Below is the full request xml. I can include the server template json if needed. I have read the following documentation: Send an Envelope from a Template, Dev Center Templates Doc, and Rules for CompositeTemplate Usage.
...ANSWER
Answered 2017-Dec-12 at 18:45You can add document in an envelope from either server template or Inline Template. If you are adding document from InlineTemplate then you should define the tabs using anchor string and all the tabs will be created using InlineTemplate only. You cannot mix two strategies, i.e adding few tabs from server templates and few tabs (using Anchor String) from Inline Templates. If you have same document in both server and inline template then create envelope using InlineTemplate and create recipient tabs using anchor string, I am not able to understand why you are mixing one recipient from Server and another from Inline Template.
QUESTION
I am using DocuSign demo account to send a document as an email for signing to the client using C#. I am using the code in this link (https://www.docusign.com/developer-center/api-overview#quickstart) to do that. But when I run the code it is not sending any email to the client and it is not showing any error too. I also tried posting the baseurl that it returns after authentication along with the envelope using HttpWebRequest and also with ajax. It didn't worked out too. Can anyone please help me with this ?
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.IO;
using Newtonsoft.Json;
using DocuSign.eSign.Api;
using DocuSign.eSign.Model;
using DocuSign.eSign.Client;
namespace DocuSignTest {
...ANSWER
Answered 2017-Nov-14 at 20:45I'd suggest that you comment-out (or remove altogether) this line from your code:
signer.ClientUserId = "1234";
When you specify ClientUserId, you're telling DocuSign not to send an email to the signer (because that signer is what DocuSign refers to as an embedded recipient). If you remove ClientUserId, you're telling DocuSign that the signer is a remote recipient, so DocuSign will send a signing invitation email to that recipient.
QUESTION
After all the neccesary steps in Sandbox/Demo account my Integrator key was marked Live and I attached it to live account.
I am using DocuSign PHP SDK so I changed API username, API password, API account ID and Host to Live account credentials according to this guide - Post Go Live steps.
Anyway I am getting error 401 Unauthorized when attempting to create Envelope (or anything else).
...ANSWER
Answered 2017-Nov-03 at 14:23When going live while using DocuSign PHP SDK, set Host parameter to https://eu.docusign.net/restapi
or any other subdomain provided by DocuSign that suits you best (eu, na1 ,na2, etc...).
When working with DocuSign PHP SDK, you don't need to do login request to retrieve baseUrl
parameter for your actual request (ex: creating Envelope). Instead you set Host parameter right at the beginning of your code and don't care about baseUrl
anymore.
And that is where the problem lies. WITHOUT SDK, you first do login request to https://www.docusign.net/restapi/v2/login_information
to get back your baseUrl
paramater (ex: https://eu.docusign.net/restapi/v2/account/1234/envelopes
) and use that for actual request. So when working WITH SDK, set the subdomain of Host parameter to eu, na1, na2 or any other valid value provided by DocuSign right away.
I found the solution thanks to this answer: https://stackoverflow.com/a/44119359/3970975
QUESTION
Thanks in advance for any and all help.
I am trying to implement "legacy header authentication" as described on this page: https://docs.docusign.com/esign/guide/authentication/legacy_auth.html
I have my email address, password, and integration key pieced together in the X-DocuSign-Authentication header as follows:
...ANSWER
Answered 2017-Oct-10 at 17:56It seems you are behind a proxy or your firewall is not allowing to hit docusign api endpoints, because above error details is coming from McAfee, node has value McAfee Web Gateway - Notification - Authentication Required, so some authentication is required by your McAfee to allow traffic to DocuSign API endpoints. Please check with someone in your IT team to get this resolved
QUESTION
I am trying to send an envelope request using this tutorial. I am using NodeJS trying to hard code the PDFFile in base64Format but I am getting the PDF_VALIDATION_FAILED. This is my code:
...ANSWER
Answered 2017-Aug-10 at 23:41You should also specify Content-Transfer-Encoding: base64
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install developer-center
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page