This topic contains 1 reply, has 2 voices, and was last updated by  mwilliams 6 days, 13 hours ago.

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

    I am making the following call

    https://sandbox.esignlive.com/api/packages/uUoiB-Htq5GXIvRN9VeDcjrMXYE=/documents/default-consent/approvals/b838ff5f-d63e-4a63-af92-fb2ec7fe9b98/sign

    and sending in the payload the following:

    {
    	"fields" : {
    	},
    	"id": "default-consent",
    	"role": "034b2399-bc09-4a3a-9f09-7ee9af853211"
    }
    

    And in the response I get

    ...
            accepted: '2018-07-10T10:54:25Z',
            signed: null,
    ...
    

    So my question is what is the call I need to make to set this to signed, since as we can see the signed field is still null.

    • This topic was modified 6 days, 22 hours ago by  Motard.
    • This topic was modified 6 days, 21 hours ago by  Motard.
    • This topic was modified 6 days, 21 hours ago by  Motard.
    • This topic was modified 6 days, 21 hours ago by  Motard.
    Keymaster
    mwilliams
    Guru
    Member since: 21.08.2015
    Number of posts: 847

    Score

    0

    Hey Motard,

    The best solution for signing on behalf of your signer is to utilize the method that Duo pointed you to in your other post:

    This signature is not assigned to you for signing. response

    Using the REST API to sign on behalf of your signer can be found in the following guide:

    Bulk Sign for a Signer

    Simply passing this payload in that call would sign the default-consent document:

    {
      "documents": [
        {
          "id": "default-consent"
        }
      ]
    }

    If you do not have fields that need to be filled out in any other documents, you can add them to the payload, like so:

    {
      "documents": [
        {
          "id": "default-consent"
        },
        {
          "id": "documentID1"
        },
        {
          "id": "documentID2"
        }
      ]
    }

    To make the document IDs easier to fill out in your payload, you can specify a custom document ID when creating your transaction. This way, you don’t have to find out the random ID assigned to the document by OneSpan Sign.

    Also, remember that with the OneSpan Sign REST API, you will need to get a session token for the appropriate signer, as mentioned in the guide above, to call the auto sign endpoint for the signer.

    Hopefully this solves your issue. Please let us know.


    – Michael
    Partner and Developer Technologies Manager, OneSpan
    Facebook – https://www.facebook.com/michael.williams1120
    Twitter – https://twitter.com/mwilliams1120
    LinkedIn – https://www.linkedin.com/in/mwilliams1120

You must be logged in to reply to this topic.