.NET SDK

What parameter can I use on a capture tag, to set the fromfile value to true.

I cannot find it anywhere. This is what I've tried, but it is not a valid parameter:

{{esl:signer1:capture:size(200,50),fromfile(true)}}

Or is there a way that I can modify all capture fields in a new package using the .NET SDK with text extraction, to use the SetFromFile(true) method, without knowing the names of the capture fields in the document?

Thanks in advance. 

I need to get the details for eSign email bounce, I am pretty new using the .NET SDK, coudl you provide a snippet or pointing me to the right direction?

I downloaded the OneSpanSign.Sdk.Samples project, can I use one of the samples for this?

Hi Team,

I am integrating the Callback API for Event Notifications,

Could you please provide the list of properties available in the JObject.

For more details, refer the below screenshot.

I've noticed that the MaxPageSize value in the PageRequest class has the value of 50,  but I believe the maximum number of transactions (and presumably other items) that can be returned in a request to the API is 100 Retrieving a List of Transactions | OneSpan Community Platform. Is there a reason for this discrepancy?

Hello,

We are using the .NET SDK to setup transactions with documents containing only signature fields.  We are using Text Tag extraction as our signature locator and I attached the code we are using to do this.

We use SSO so we don't sending out the invitation for users to activate their accounts.  How can I programmatically activate the accounts using the .NET SDK.  I can determine who's pending from the list of senders, but not sure how to update their status to ACTIVE.  

We have used the invitation utility but want to automate the process.

The customer keeps getting random OneSpan signature failures when users try to send a document for signature. The same transaction works sometime and not others.   

1. Is there documentation of the error codes from Onespan and possible causes ? 

Here is a sample error returned from OneSpan rejecting the package, but the message is cryptic as to the cause.

I have a situation where I set delegation to a sender using code that has worked in the past.  The indication was that the delegation was successful BUT it didn't work.  Looking in the UI I figured out that the users had used delegation before and it has expired.  when I reassigned delegationI need to update the expiration date.  What should I do to fix this Remove the delegation so when I assign the new one it won't have an expiration date OR assign the delegation with a new expiration date?

We seem to be having an issue where we don't seem to pull in any of our recent test files using either the GetPackages or the GetUpdatedPackagesWithinDateRange.  We DO get results using those as long as we move the date range back to at least last November.  The catch is that if we use the transfer ID created when the documents are signed and sent in, we can pull in that package through the api.

I know how to get subaccount api keys but how do I get a senders API key.  The user has left State employment so I can't have them just login and give it to me.   I don't see it in the Sender structure.