OneSpan Sign Developer: Data Retrieval
In this blog, I will go over what you might have missed in the OneSpan Sign Developer Community during the week of February 12th, 2018. Let's get straight to it.
Fields enable the placement of additional data in a document at the time of signing. Fields can be placed anywhere inside a document and each field is linked to a particular signature. For example, you can add a textfield on a document for a signer asking for his or her address. Hence, once a document package has been completed, it may be useful to retrieve the values entered in certain fields (e.g. for reporting purposes). You can follow this guide on how retrieve field summaries.
OneSpan Sign provides you with the ability to add senders to your account, allowing them to create and send document packages (transaction in the new UI) for signature. As an account owner, you will have access to the packages created by your senders. Though, you’ll only be able to retrieve the packages created by your senders through the SDKs/API. Namely, you will need to use the Completion Report. If you want to access from the UI the packages created by your senders, you will need your senders to delegate access to you. This is also the case for the reverse situation. For more information on delegating access, see this guide.
OneSpan Sign Environments
Finally, when making API calls to OneSpan Sign, you will need to make sure that you reference the correct instance. Otherwise, you'll be thrown an unauthorized error. You can find all the API URLs in our documentation page. Link to Post If you have questions regarding this blog or anything else concerning integrating OneSpan Sign into your application, visit the Developer Community Forums: developer.esignlive.com. That's it from me. Thank you for reading! If you found this post helpful, please share it on Facebook, Twitter, or LinkedIn.