REST API

Are there any known issues with using both methods of extraction in the same document?

The following package has been created in the sandbox: zc1pssVwepH2BDjC0-lDlbuNzD8=

The last document in the package contains a mix of Text Anchors along with Text Tags embedded in the PDF. The anchors are used to provide 3 text fields that the entered data will be utilized post-completion. The Text Tags are used because the same signature block appears in a few different documents, so copying and pasting the entire group across has made maintenance easier.

Hey guys, 

I'm trying to put together the following flow:

1. Create a Package through Postman using the following payload.
2. Add a document through a azure function (Its working).
3. Update Package from Draft to Sent by making a Put request with only { "status": "SENT" }.

The last step always returns 

{

    "messageKey": "error.validation.sendPackage.noApprovals",

Hi Team,

I have attached list of files which I have downloaded through APIs, but it seems that some of the files doesn't have any metadata files.

Now I have only the name of the documents, I don't have package id, and I need few information that is only available in metadata.

Can you please help me out, If there is any API that can provide me the metadata file names based on the document name?

Thanks

Rohit

If we wanted to NOT put a logo but place a barcode on the evidence summary template can we do that for eSignLite. 

We want our OCR technology to be able to pick up that it's an evidence summary document and perform straight through processing. 

Hi,

I tried using the API Key (specified under the Authorize button) from under the sandbox account (not the Client ID & Secret) with the swagger page (https://community.onespan.com/products/onespan-sign/sandbox#/) where different calls can be tried out. However, the API key is not accepted. This is the response:

{ "messageKey": "error.unauthorised.noSession", "message": "Failed to retrieve Session", "code": 401, "name": "Unauthorized" }

Is there anything additional that needs to be done to use the swagger page?

Hi,

  I'm trying to send an extra document to an existing package (with no document) using the REST API endpoint /api/packages/{packageId}/documents.

  Doing so returns me a "406 Not Acceptable" error, which doesn't tell me much on what is wrong.

  I've checked again and again with documentation, and my JSON has the right structure.

Hey guys,

How do we change the GMT to borrower's time zone in Evidence Summary?

Using create package API, Along with creating package, can we use also use data field to store some data.

This field value we use in when retrieve the package.

"data": {
    "additionalProp1": {},
    "additionalProp2": {},
    "additionalProp3": {}
  },

I am attaching the package request body

After doing some 11.39 SANDBOX testing; seems retrieving Sender via Email works but retrieving Sender via Sender ID does not.

{{TheHost}}/api/account/senders/1iVOFpzqGzoF
{
    "messageKey": "error.forbidden.viewSender",
    "message": "You do not have the necessary permission to view this sender.",
    "code": 403,
    "name": "Access Denied"
}

I shouldn't have security issue as I'm owner of Account.  Any idea's?

I would like to be able to save a 'role' type attribute against a group signer - for example 'Insurance Agent'. I find when I save a signer of type group, the customId attribute is not returned when I request the package. Is there an attribute I can use on a group signer that will be returned to me when I get the package? It seems the system only wants to return the groupId. From this I can get the group name and the group email, but no additional signer attributes.