REST API

Hi OneSpan team.

I'm capturing the sender's signature in my custom UI. And save it via POST call to "user.signature.handdrawn".

Could you please tell is it possible to store the color (e.g. blue) of the signature and use it further during signing ceremony and in the signed pdf?

I see there is "user.signature.handdrawn.textual.color" field. Could you please tell me what is this field and what is used for?

Thanks!

Illia

I have placed a signing date tag the top of my document. The document essentially reads "this is effective as of {{esl:Signer1:SigningDate}}." When we open the signing ceremony this is blank and just leave a large space in between the words and is leading to confusion. With docusign and other tools the date would be prepopulated already like in the screenshot I've attached. Is this possible with OneSpan?

Hi,

I am wondering if it is possible gather signer inputs in input fields after signing via the API? We are looking to store text inputs and radio button selections.

I'm trying to figure out how I can identify which signer has signed when I receive signer_complete event. 

It sends:

{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"SIGNER_COMPLETE","sessionUser":"7f102e73-2cbf-414b-85b6-0814927379ef","packageId":"amAPA2Bs3mWdWEPM9S1p0aGlip8=","message":null,"documentId":null,"createdDate":"2023-11-19T00:25:57.632Z"}

I assume the sessionuser is how I can identify the signer but I'm not sure how to retrieve the guid in order to match it to what is sent in the event. Is there a GET I can use?

Hi,

I'm having a problem. When I define the payload to create the transaction, OneSpan overrides the attachment ID.

For example, the user is required to attach 2 documents.

In the first document I want it to have the "Id" 00012345 and in the second, the "Id" should be 00012346.

However, once the transaction is created, when querying the transaction information, the originally defined attachment IDs, OneSpan overrides it

How can I prevent OneSpan from overwriting attachment IDs?

I am running into an issue with my radio button group. I have selected one of the required options but when I try to complete signing I get an error that says "Not all approvals have been confirmed" I have attached a screenshot. Here is my JSON:

{

  "roles": [

I'm sending transactions on behalf of other users through the API. 

I have the users set up with Role Sender. I was able to successfully send on their behalf in our testing onespan environment. 

When I try to send a transaction on their behalf through API in production, I get this error

CongaSign.SignException: {"code":403,"messageKey":"error.forbidden.noPermission","message":"The required permission was not found.","name":"Access Denied"}

I'm trying to figure out how to resolve this error

I've noticed in the UI I am able to add tooltips to my radio buttons. I am wondering if this is a possible in the api as well ie

{ "id":"signer1_group1_radio1", "name":"signer1_group1_radio1", "type":"INPUT", "subtype":"RADIO", "page":0, "height":15, "width":15, "left":100, "top":100, "value":"X", "validation":{ "required":true, "group":[ "group1" ] } }

Hi is it possible using the REST API to disable the activation email at the transaction level? For certain transactions we want to send the activation email but for others we are serving the signing URL and don't want the activation email sent. Can I specify whether we want the email sent or not in the JSON?

I was able to sign a document when a signer is assigned to a signbox using API.
But the same users sign is not possible when the singer belongs to a group.

is there any restriction to sign via APIs for groups?

API response is 200 for both. 

API: https://sandbox.esignlive.com/api/packages/<transaction_id>/documents/signed_documents