Forums

We are attempting to make fields read only in our OneSpan package.  We are trying to use the API to mark them.  We cannot find the way to mark dates read-only.  
The preference would be to mark them read only using the API, so that they all work similarly.
We are actually attempting to bypass setting the fields within the PDF and marking them read only via the payload. 

Forums

Hello. I am new to using Onespan Sign API. I am using Rest API and Postman to enter and execute the code. Please see the below code. I am trying to add a field onto an existing package id. I have included the details below. How do I add a field to a Onespan Package? Can you please send me a complete code sample? I am new to using the API and still learning, so I do not know how to enter peice by peice yet. 
curl -X 'POST' \

Forums

I checked the guides and no matter what i do i am getting the error below on postman the url i used was https://sandbox.esignlive.com/oauth . I have created an app and have the client id and secret with me, i want to know which URL to hit and what parameters to send in order to get the access token

<html>

 

<head>

    <title>400 Bad Request</title>

</head>

 

<body>

    <center>

Forums

I'm trying to place signature using the text anchors in Payload in API Body by referring the blog(OneSpan Sign How To: Using Text Anchors | OneSpan), but I'm getting the below validation error (Currently testign this in Postman), Also attaching the Document that has to be uploaded.

Error

{

    "messageKey": "error.validation.validateApproval.noRolesOnApproval",

    "parameters": {

Forums

could you please help me why i'm getting this error, here i want to request for signing only one document and one signer. Attached the file for which i'm testing.

 

{

"documents": [

{

"approvals": [

{

"id": "ClientSignature",

"role": "Signer1",

"fields": [

{

"page": 0,

"top": 200,

"subtype": "LABEL",

"height": 50,

"left": 100,

"width": 200,

"id": "myLabelField",

"type": "INPUT",

"value": "Example label field value"

},

Forums

Is it possible to update the handover urls everytime a different user accesses the package? We have users who will access the document via sa personalised URL and we are hoping that after signing it would navigate them back to their personal url.

The idea that I have is that once the user access his personalised url, a web service gets initialised to update the handover url, so when he proceeds to sign the document, clicking return would navigate him back to his personalised url.

Is this possible? I'm currently getting 405 error when I try to do it.

Thank you!