This topic contains 3 replies, has 2 voices, and was last updated by  Duo_Liang 2 weeks, 4 days ago.

  • Author
    Posts
  • Participant
    Motard
    Newbie
    Member since: 05.07.2018
    Number of posts: 8

    Hello I created a package but removed the Electronic Disclosures and Signatures Consent.

    So I have a package with just one document. But when I try to sign it using the api call /packages/package_id/documents/signed_documents, I am not able to sign the document.

    What could the issue be here?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 183

    Score

    0

    Hi Motard,

    If signature approval(s) in document is assigned for a signer, you’d use Bulk Sign Feature instead of Sign Documents Feature.
    As Sign Documents is designed for signing for a sender(in API call, you just need a package id and no need for any role id) while Bulk Sign is designed for signing for a common signer.(you will follow three steps to retrieve session token for a signer and use this token to bulk sign)

    Hope this could help you!

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    • This reply was modified 2 weeks, 4 days ago by  Duo_Liang.
    Participant
    Motard
    Newbie
    Member since: 05.07.2018
    Number of posts: 8

    Score

    0

    Maybe, I did not make myself clear. I know I only wish to sign a document, and I thought I could use Bulk Sign API call to sign that document.

    The problem is that I am not able to sign the document with the Bulk Sign API call. Could this have anything to do with the fact that I removed the Electronic Disclosures and Signatures Consent?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 183
    Approved answer

    Score

    0

    Hi Motard,

    Sorry about my expression, I may have made you confused.

    If you have checked with both of these two features(sign documents vs bulk sign), you’d find that POST /api/packages/{packageId}/documents/signed_documents this call is both used in these two features. The difference is, in last step of bulk sign, you will put signer’s session token into the request header so that OneSpan Sign would know why you want to sign on behalf of. Put it in another way, if you still using your API Key as an authorization token, OneSpan Sign would consider you are sign for your sender(if your sender is not the signer, it won’t work without any error)

    And please make sure you put the right document ID in your request payload.

    As to your question, if the remove of consent document could cause any problem, I have tested the same case for you and seems everything works well.

    Please tell me if you still encountered this problem. And hope this could help you!

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist

You must be logged in to reply to this topic.