Document Callback Response

  • 1
  • Problem
  • Updated 9 months ago
We are using both Right Signature versions for document status.

In older version we are getting the signatory name and email address in response as provided below. (https://rightsignature.com)

<?xml version="1.0" encoding="UTF-8"?>
<callback> <callback-type>Document</callback-type> <guid>DOCUMENTGUID</guid> <redirect-token /> <status>recipient_signed</status> <recipient> <name>James Painter</name> <email>xxxxxx@xxx.com</email> </recipient> <created-at>2019-02-14 08:38:10 -0800</created-at> <signed-at>2019-02-15 07:43:47 -0800</signed-at> </callback>
But in newer version, we are getting the call back response as below (https://api.rightsignature.com/public/v1/)
{
"callbackType" : "Document",
"id" : "e4a2db99-dcb1-4c06-8e6b-237d720dcae2",
"event" : "signed",
"documentState" : "pending",
"status" : "pending",
"createdAt" : "2019-02-06T05:26:11.868-08:00" }
Is there any reason that signer name and details are not available in json? How to identify the signer from call back ?

Any help / response would be appreciated.
Photo of Kannan Chandrasekaran

Kannan Chandrasekaran

  • 24 Posts
  • 0 Reply Likes

Posted 9 months ago

  • 1
Photo of Saravanan Kannan

Saravanan Kannan, Software Engineer

  • 82 Posts
  • 12 Reply Likes
Hi Kannan,

One way would be do a GET to this end point 
GET /public/v1/documents/:id (https://api.rightsignature.com/documentation/resources/v1/documents.en.html) with the id from the callback, then you would get the details about that document. Hope this helps.

Thanks
Saravanan
Photo of Kannan Chandrasekaran

Kannan Chandrasekaran

  • 24 Posts
  • 0 Reply Likes
Thanks for your quick reply. We are already using this endpoint to get the response. Below is the audit we got for a test document.

 "recipients": [
      {
        "role_name": "b",
        "name": "pandikannan@anbsystems.com",
        "email": "pandikannan@anbsystems.com",
        "status": "signed",
        "id": "90b40979-7264-49c5-abf3-ca09c9de3e0c",
        "sign_url": "https://secure.rightsignature.com/signers/90b40979-7264-49c5-abf3-ca09c9de3e0c/sign?access_token=zFVgSQjZnWaPmr8cepfs",
        "remind_url": "https://api.rightsignature.com/public/v1/signers/90b40979-7264-49c5-abf3-ca09c9de3e0c/reminders",
        "message": null,
        "sequence": 1
      },
      {
        "role_name": "a",
        "name": "pandikannan@anbsystems.com",
        "email": "pandikannan@anbsystems.com",
        "status": "signed",
        "id": "fd8daf8d-6769-4900-aef6-180c9d6c4f47",
        "sign_url": "https://secure.rightsignature.com/signers/fd8daf8d-6769-4900-aef6-180c9d6c4f47/sign?access_token=STxvCLwJ1n8oGy-XV739",
        "remind_url": "https://api.rightsignature.com/public/v1/signers/fd8daf8d-6769-4900-aef6-180c9d6c4f47/reminders",
        "message": null,
        "sequence": 0
      }
    ],
    "audits": [
      {
        "payload": "All signers have signed and the document is now executed. Copies have been sent to pandikannan@anbsystems.com and pandikannan@anbsystems.com.",
        "keyword": "executed",
        "timestamp": "2019-02-06T13:28:00.000+00:00"
      },
      {
        "payload": "pandikannan@anbsystems.com (pandikannan@anbsystems.com) signed the document on Chrome via Windows from 122.183.251.121.",
        "keyword": "signed",
        "timestamp": "2019-02-06T13:28:00.000+00:00"
      },
      {
        "payload": "pandikannan@anbsystems.com (pandikannan@anbsystems.com) authenticated via email on Chrome via Windows from 122.183.251.121.",
        "keyword": "identity_authenticated",
        "timestamp": "2019-02-06T13:28:00.000+00:00"
      },
      {
        "payload": "pandikannan@anbsystems.com (pandikannan@anbsystems.com) viewed the document on Chrome via Windows from 122.183.251.121.",
        "keyword": "viewed",
        "timestamp": "2019-02-06T13:28:00.000+00:00"
      },
      {
        "payload": "pandikannan@anbsystems.com (pandikannan@anbsystems.com) was emailed a link to sign.",
        "keyword": "distribution",
        "timestamp": "2019-02-06T13:27:00.000+00:00"
      },
      {
        "payload": "pandikannan@anbsystems.com (pandikannan@anbsystems.com) signed the document on Chrome via Windows from 122.183.251.121.",
        "keyword": "signed",
        "timestamp": "2019-02-06T13:27:00.000+00:00"
      },
      {
        "payload": "pandikannan@anbsystems.com (pandikannan@anbsystems.com) authenticated via email on Chrome via Windows from 122.183.251.121.",
        "keyword": "identity_authenticated",
        "timestamp": "2019-02-06T13:27:00.000+00:00"
      },
      {
        "payload": "pandikannan@anbsystems.com (pandikannan@anbsystems.com) viewed the document on Chrome via Windows from 122.183.251.121.",
        "keyword": "viewed",
        "timestamp": "2019-02-06T13:27:00.000+00:00"
      },
      {
        "payload": "pandikannan@anbsystems.com (pandikannan@anbsystems.com) was emailed a link to sign.",
        "keyword": "distribution",
        "timestamp": "2019-02-06T13:26:00.000+00:00"
      }
    ],
In some scenario, we are sending the document to signer again in order. In example above, same signer is signing in two different places of document that is followed in signatory order. The signature part is working fine. In audit, it shows that user has completed, since the user email address is same. Is there a way to link, which signer has signed in audit...

Thanks for your help.
Photo of Saravanan Kannan

Saravanan Kannan, Software Engineer

  • 82 Posts
  • 12 Reply Likes
Kannan,

Is it showing the document as executed after one signer has signed (signer 2 has not signed), since you send to the same email for two signers? Or you just need a way to differentiate in the audits.

In latter case, I would use Signer - seq 1 and Signer - seq 2 in the name of signer names and the audit would show them even if the email is same. This is just a suggestion.

Thanks
Saravanan
Photo of Kannan Chandrasekaran

Kannan Chandrasekaran

  • 24 Posts
  • 0 Reply Likes
Hi Saravanan,

We tried by changing the name. But, in email it appears as Signer 1, Signer 2. Can we change the email template keyword ?

And as you stated, do we have way to differentiate in audits ? With that, we can show the audit information of signers. Still the document status shows as pending, which is correct.

Thanks, 
Kannan
Photo of Saravanan Kannan

Saravanan Kannan, Software Engineer

  • 82 Posts
  • 12 Reply Likes
Kannan,

No, there is a not a way to differentiate them in audits. Does changing settings in email branding help?

Thanks
Saravanan
Photo of Kannan Chandrasekaran

Kannan Chandrasekaran

  • 24 Posts
  • 0 Reply Likes
Hi Saravanan,

Thanks for your reply.

If we cannot do at audit, can we get identifier in the callback response on document status with user information? We can make use of that to solve our problem.

Details: User Name, Email and Sign Order ?

{
"callbackType" : "Document",
"id" : "e4a2db99-dcb1-4c06-8e6b-237d720dcae2",
"event" : "signed",
"documentState" : "pending",
"status" : "pending",
"createdAt" : "2019-02-06T05:26:11.868-08:00"
}

Thanks,
Kannan