REST API

Hi Team,

We are using the OneSpan REST APIs to integrate OneSpan into our e-signature journey.

We have a requirement to display the signing status of each signer for a given package/transaction. In our setup, there is typically one signer per role.

I see the following possible approaches:

Option 1: Use the Signing Status API

I can call:

GET /api/packages/{packageId}/signingStatus?signer={signerId}

The signerId can be obtained from:

GET /api/packages/{packageId}

Hi OneSpan Team,

I’m working on an integration for OneSpan Sign and need to confirm available API capabilities for signer reminders.

Requirement

• We have a package/transaction with multiple signers.
• We need to trigger reminder notifications from our application for multiple signers in one user action.
• Preferred behavior: provide only packageId (or package + list of signers) and have OneSpan send reminders to all eligible/pending signers in one API call.

What we found so far

Hi Team

User wants to have signing time along with singing date. Team found there is a text tag esl:InsuredSigner1:SigningDate to print signing date. The tag signingdate prints only date and not the time.

Is there a possible configuration to print time along with the date using the text tag.

We also tried enabling Timestamp for signatures in OneSpan Settings and it appears the user wants date and time below the signature. Text tag helps achieve this using position offset, etc.

Hello,

Since August 6th,  a package creation request that we haven't touched in months started failing with this error.  It happens only in the sandbox environnement, the same request works correctly in production. I've reviewed the release notes for upcoming changes but nothing seems related. Is this a know issue?

We are using Rest API for creating packages out of templates.

I can't seem to get oAuth2 working so I'm wondering if anyone has.    All my attempts for token retrieval end in a 401 with an invalid_client response.    I'm sure my account is setup correctly and the values are being sent correctly in the auth call.

I would like to know how to record or archive the signer’s name into the "Other" column of the audit trail for each signing action completed.
Currently, the audit trail logs the signing actions, but it just show approval ID in "Other" field, I want the signer’s name to appear specifically in the "Other" field associated with "Capture Signature" event.
Is there a standard approach, configuration, or API customization that can achieve this?

Any guidance or best practices would be appreciated!

Can anyone provide a request to disable an active listener? 

Users just started reporting an error code when trying to send a signature to a customer.  "The supplied input cannot be parsed"  Any clues as to what the issue could be? Is this a salesforce error or OneSpan?

Sending a POST request to /api/callback to update the callback key, callback events and callback URL returns:

 Client error: `POST https://sandbox.e-signlive.ca/api/callback` resulted in a `400 Bad Request` response:
{"message":"Invalid JSON.","code":400,"technical":"Failed to deserialize json string to target type com.silanis.esl.api. (truncated...)

I'm using Guzzle's `json` options to automatically json_encode the object. Even using POST body with JSON encoded string does not work.