Group Signing using APIS
Monday, November 20, 2023 at 02:07amI was able to sign a document when a signer is assigned to a signbox using API.
But the same users sign is not possible when the singer belongs to a group.
is there any restriction to sign via APIs for groups?
API response is 200 for both.
API: https://sandbox.esignlive.com/api/packages/<transaction_id>/documents/signed_documents
curl --location --request POST 'https://sandbox.esignlive.com/api/packages/<transaction_id>/documents/signed_documents' \
--header 'Authorization: Basic <api_key>' \
--header 'Content-Type: application/json' \
--data-raw '{ "documents": [
{"id": "<document_id>" }
],
"handdrawn":"<base64 of signature>"
}
Reply to: Group Signing using APIS
Monday, November 20, 2023 at 09:19amHi Sohan,
Thanks for your post!
Before we discuss further into this issue, could you briefly explain your use case? If you simply want to automatically place a signature to the document, will a signer with group email work?
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Group Signing using APIS
Monday, November 20, 2023 at 11:16pmThanks for your reply
We have a integration with one span sign to sign the document on click (through automation - bulk sign for similar transactions).
Any one of multiple signer can sign the document and transaction will be completed.
we have used groups to facilitate this current workflow.
Reply to: Group Signing using APIS
Tuesday, November 21, 2023 at 08:40amHi Sohan,
Thanks for the background information.
Actually I am experiencing the same behavior as you described that the bulk sign call returned 200 but the document didn't get signed. You can fill in a support ticket ([email protected]) and ask for confirmation whether this is by designed.
As a workaround, you can first set the signer f/lname and email to a generic group name and email, then update the recipient information via API when the signer is ready to sign:
PUT /api/packages/{packageId}/roles/{role_id}
{
"signers": [
{
"email": "[email protected]",
"firstName": "updated_fname",
"lastName": "updated_lname"
}
],
"id": "Signer1",
"name": "Signer1"
}
PS: You will not be able to update recipient information once the signer has started to sign.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer