565 results matched your search criteria
Forum topic
OneSpan Sign
We currently received notifications when the package is completed "PACKAGE_COMPLETE" however the documentid property is null.
Forum topic
OneSpan Sign
Note: I saw this forum post but it wasn't really giving an answer so I am starting a new one to see if we can figure this out.
Forum topic
OneSpan Sign
Good afternoon, when generating the download of documents through the OSS - Transaction Export & Download Tool .jar, not all the supports that were signed on the web are evident
Forum topic
OneSpan Sign
Hi, i am trying to use the POST api /api/packages/{packageId}/attachment/{attachmentId} to add an attachment to a package but i always receive the below reply.
I am testing it through the swagger of the community portal. Any idea on the reason of the error?
Forum topic
OneSpan Sign
Would like to check if there's a way to use a template and programmatically populate custom fields or labels for information like Policy #, Customer Name & Address, and any other transaction-specific details.
Forum topic
OneSpan Sign
Hi,
On the DOCUMENT_SIGNED callback is it possible to know who has signed the document directly or in some other way indirectly?
I need the email of the person who has signed the document for our application workflow.
What can I do with the sessionUser attribute.
Example Payload:
{"@class":"com.si
Forum topic
OneSpan Sign
I haven't started working on the code to handles callbacks yet. I was looking at http://docs.e-signlive.com/doku.php?id=esl:e-signlive_guide_event-notification and saw the SIGNER_COMPLETE notification.
Forum topic
OneSpan Sign
Guys,
Is there something going on with the API servers? I'm getting this weird error when trying to upload documents that I know worked.
-------------------------------
MessageKey: error.internal.default
Error Message: Unexpected error.
Forum topic
OneSpan Sign
I have looked all through the SDK and the REST API, and I can't find an answer to this. Could you please assist me?
In your notifications you send us a package id, a session user id, and the event name.