I'm making a request to /accounts/{accountId}/envelopes/{envelopeId}/views/recipient
with the JSON
{
"authenticationMethod": "userid",
"returnUrl": "http://localhost:3000/rooms/07bfcdf24f455ff14964f0e14c8d6825/finished",
"userId": "5a44ea44-02be-4926-8c3d-66cb85523799"
}
and getting the error
{
"errorCode": "INVALID_REQUEST_PARAMETER",
"message": "The request contained at least one invalid parameter. The value of AuthenticationMethod is invalid."
}
EDIT:
Another thing i failed to mention, is the envelope was created with compositeTemplates.
From the SOAP WSDL (https://www.docusign.net/api/3.0/dsapi.asmx?wsdl) - these values also work for REST (lowercase):
Password
Email
PaperDocuments
HTTPBasicAuth
SSLMutualAuth
X509Certificate
Kerberos
SingleSignOn_CASiteminder
SingleSignOn_InfoCard
SingleSignOn_MicrosoftActiveDirectory
SingleSignOn_Passport
SingleSignOn_SAML
SingleSignOn_Other
Smartcard
RSASecureID
Biometric
None
KnowledgeBasedAuth
The following values should all be valid, though note that this might not be a full list:
"None"
"Email"
"Password"
"HTTPBasicAuth"
"X509Certificate"
"KnowledgeBasedAuth"
Related
I'm trying to make a API call to the eSignature REST API Envelopes: listStatus (as shown here)
However, I get ERROR 400 Bad Request and the following:
{
"errorCode": "UNSPECIFIED_ERROR",
"message": "Object reference not set to an instance of an object."
}
Even trying it in DocuSign's API explorer I get the same error. The error seems to be pointing to a issue with how the request body is formed. DocuSign suggests this,
{
"envelopeIds": [
"44c5ad6c-xxxx-xxxx-xxxx-ebda5e2dfe15",
"8e26040d-xxxx-xxxx-xxxx-1e29b924d237",
"c8b40a2d-xxxx-xxxx-xxxx-4fe56fe10f95"
]
}
however, if I use "envelopeIds" in the body instead I get:
{
"errorCode": "INVALID_REQUEST_PARAMETER",
"message": "The request contained at least one invalid parameter. Query parameter 'from_date' must be set to a valid DateTime, or 'envelope_ids' or 'transaction_ids' must be specified."
}
replacing "envelopeIds" with "envelope_ids" I get:
Response:
{
"errorCode": "UNSPECIFIED_ERROR",
"message": "Object reference not set to an instance of an object."
}
and even using a comma separated list like, I get the same error:
Body:
{ "envelopeIds": "44c5ad6c-xxxx-xxxx-xxxx-ebda5e2dfe15,8e26040d-xxxx-xxxx-xxxx-1e29b924d237"}
Response:
{
"errorCode": "UNSPECIFIED_ERROR",
"message": "Object reference not set to an instance of an object."
}
Any help would be much appreciated. I have tried this using both postman and DocuSign's API explorer.
You need to include ?envelope_ids=request_body in the URL.
Then it should work with the body:
{
"envelopeIds": [
"44c5ad6c-xxxx-xxxx-xxxx-ebda5e2dfe15",
"8e26040d-xxxx-xxxx-xxxx-1e29b924d237",
"c8b40a2d-xxxx-xxxx-xxxx-4fe56fe10f95"
]
}
I am using the Graph API to get details from business users. Since most of the Profile is Non-Business, would like to find-out, if there is an API to get the Profile Type?
During the trial, I keep getting the following message and also discovered sometime the API is misbehaving..
{
"error": {
"message": "Invalid user id",
"type": "OAuthException",
"code": 110,
"error_subcode": 2207013,
"is_transient": false,
"error_user_title": "Cannot find User",
"error_user_msg": "The user with username: rohit_xxx cannot be found.",
"fbtrace_id": "FkKgUvBdJWZ"
}
}
So, If I know the Profile Type in advance, We can handle the response in much better way..
Thanks in Advance..
The instagram Graph API is designed to work with creator/business accounts. This is specified in multiple places.
If a user doesn't have business/creator account, the instagram id would be empty in the response.
curl -i -X GET \
"https://graph.facebook.com/v3.2/{fb-page-id}?fields=instagram_business_account&access_token={access-token}"
Response:
{
"instagram_business_account": {
"id": "" // Connected IG User ID
},
"id": "134895793791914" // Facebook Page ID
}
The recipient name has an umlaut character -> "François"
While sending the envelope to this recipient using the Docusign Rest API v2, I'm getting an error in response with
Error Code -> UNSPECIFIED_ERROR
Error Message -> An item with the same key has already been added.
If I change the recipient's name to a string with no umlaut characters, the envelope works.
Is there any way to fix this at an account level or while sending the request to Docusign?
Following is the request xml which works without the umlaut character ç in the recipient's name.
<envelopeDefinition><emailSubject>Agreement Name</emailSubject>
<status>sent</status><documents><document><name>Agreement Name</name>
<documentId>368649304</documentId><documentBase64>Document
Contents</documentBase64></document></documents><recipients><signers>
<signer><recipientId>1</recipientId><email>TestEmail</email>
<name>François Harnandez</name>
<routingOrder>1</routingOrder><tabs><signHereTabs><signHere>
<anchorString>ICLM_ExtSignature:1</anchorString></signHere></signHereTabs>
<dateSignedTabs><dateSigned><anchorString>ExtDate1</anchorString>/dateSigned>
</dateSignedTabs></tabs></signer></signers></recipients>
</envelopeDefinition>
I just tested this to see what I actually passed to the CURL request and here's what I get (json instead of xml) when I pass in Tèst User as a recipientName
Request
POST: https://{server}/restapi/v2/accounts/{accountId}/envelopes/
{
"emailSubject": "Testing",
"templateId": "{templateId}",
"status": "sent",
"templateRoles": [
{
"email": "email#domain.com",
"name": null,
"roleName": "Role 1",
"clientUserId": 12345654321
}
]
}
Response
{
"errorCode": "INVALID_USERNAME_FOR_RECIPIENT",
"message": "The user name for the recipient is invalid. The user name is invalid for recipient email email#domain.com"
}
I would expect this error message to come back if I'm passing in a null value, is your XML encoding stripping out that value? Can you see what you're actually passing to DocuSign with an entire response?
Could you try this request in JSON instead of XML ?
I have try in JSON with name "François" and I have no problem to send the request and to sign with this name : http://i.stack.imgur.com/vtWUc.png
I have following request to be sent to DocuSign API,
"emailSubject": 'DocuSign API - Signature Request on Document Call',
"documents": [{
"name": test.pdf,
"documentId": 1,
}]
What I dont understand is, where should the documents name be present and what about the documentId.
I got an error as follows:
{ errorCode: 'INVALID_REQUEST_PARAMETER',
message: 'The request contained at least one invalid parameter. A document was defined without setting the \'name\' field.' }
Error calling webservice, status is: 400
I think it cannot find the pdf.
You should fill in a correct path into name field:
"name": "path/to/existing/pdf/test.pdf",
I'm currently testing an API call that will ultimately allow for an agent to provide signature and another party to sign in person. In sending the call via API Explorer I continue to receive the following response:
{
"errorCode": "INVALID_EMAIL_ADDRESS_FOR_RECIPIENT",
"message": "The email address for one of the recipients is not valid."
}
I've read in the REST API guide that this needs to be enabled for my account; it may be that my demo dev account does not have this enabled. I just need to verify whether or not that I'm not omitting any essential parameters in this call. I've tried passing in my email (as the account holder) and still receive this error. Here is my request body JSON:
{
"emailBlurb": "test",
"emailSubject": "test",
"documents": [
{
"name": "ChiropractorPlusApplication.pdf",
"documentId": "1"
}
],
"recipients": {
"inPersonSigners": [
{
"hostName": "Joe Host",
"recipientId": "1",
"name": "Name",
"email": "host#gmail.com",
"signerName": "Insured"
}
]
},
"status": "sent"
}
Thanks!
I believe you have found a bug with the REST API Explorer in that it's missing at least one field for In Person Signers. If you look at the REST API documentation you'll see that there's one more required parameter for In Person Signers, which is the hostEmail
Try adding to your JSON
"hostEmail" : "host's email address",
And I have a feeling that will do the trick. See page 275 of REST API v2 PDF for info on In Person Signers recipient type. It first shows a sample request with all the options then below that it lists the required fields for this recipient type:
http://www.docusign.com/sites/default/files/REST_API_Guide_v2.pdf