REST API

I am getting a 401 error when requesting an authentication token for a "SENDER" with a mixed-case email. Other places in the REST API do not require a lowercase value for email in the json.

The request I made was:

https://sandbox.esignlive.com/apitoken/clientApp/accessToken
{"clientId":"xxxxxxxxxx","secret":"xxxxxxxxxxx","type":"SENDER","email":"[email protected]"}

Canada SBX = sandbox.e-signlive.ca

API = /apitoken/clientApp/accessToken

https://sandbox.e-signlive.ca/apitoken/clientApp/accessToken

header fields Accept + Content-Type  ( both set to application/json )

Body below  with "?" instead of actual values

{

  "clientId": "???????????????????",

Hi  Team,

I need to create a package with an existing unique id (custom id)

while creating a package,

ex for package payload

{

   ----------

"name": "TEST-Package",

 "id":"1234dsfhsddfdfsghjgsdgs",

}

but getting error as

{

    "code": 404,

    "messageKey": "error.validation.packageDoesNotExist",

Guys,

I am trying to configure out settings and I see that you guys have the new signing experience, which looks awesome. Is there any way to configure the new items? I was looking through the Signing Ceremony Settings for REST API and it was still referencing the old signing experience. Do you guys have one for the new experience?

This API call requires {senderId} but when I use my "name" or "email" it does not work, nor does it work for any other value I could think of to try. The documentations says "The unique sender id" but what is that value? where does it come from? where is it on a screen?

The “packageID” seems fine, works for other API call but “SignerID” from Evidence Summary does not seem to be recognized. Its confusing as items are referred to by multiple names, e.g. PackageID appears to be the same as Signing CeremonyID and Transaction. I have only created a single Transaction at this point.

I am assuming yellow high-lighted ID is the SignerID yes/no???

Below from Evidence Summary ( see attached WORD doc )

The documentation talks about ApiKeyAuth (being deprecated) and ApiTokenAuth (recommended replacement).

Apparently a "Client Id" + "Secret" is combined to create a "Token" but I don't know how this is done for API's below.

I am not clear on "single use" vs "multi-use".

I am not clear on "sender authentication" token vs "signer"

AUTHENTICATION TOKENs calls…

Guys,

I am trying to find more information on this to see if this impacts us since we are using the callbacks. Can someone point me to an example of how this is being used/removed so that I can check if I will need to modify my code?

Thanks!

Hey all - 

I'm having trouble finding some examples for validating signers using the Q&A features. I recall seeing some examples in the docs or forums in the past but can't find them now. Any help is appreciated.  

I am trying to create a package and upload a document but I only get the error message "Number of uploaded files does not match number of documents specified in package."  I have looked through the API and other posts about this error message.  I have even tried to use the exact configuration as in this CodeShare: https://community.onespan.com/documentation/onespan-sign/codeshare/upload-document-through-multipartform-data-using-postman&nbsp