Optional signers
Tuesday, April 13, 2021 at 04:22pmIs it possible to create a template with up to 5 signers but dynamically choose how many will actually be signing the package? I created a package with 2 signers but if I only include 1 signer it throws an unassigned role error.
{
"name": "{{name}}",
"type": "PACKAGE",
"autocomplete": true,
"status": "SENT",
"roles": [
{
"id": "{{id}}",
"name": "{{name}}",
"type": "SIGNER",
"signers": [
{
"id": "{{id}}",
"firstName": "{{firstName}}",
"lastName": "{{lastName}}",
"email": "{{email}}"
}
]
}
]
}
Error:
{
"messageKey": "error.validation.packageActivation.unassignedRole",
"message": "There is a role with no signer.",
"code": 400,
"name": "Validation Error"
}
Reply to: Optional signers
Tuesday, April 13, 2021 at 06:51pmHi Namki,
Thanks for your post! If you are creating transactions out of a template using the clone call (POST /api/packages/{template_id}/clone). I believe you'd have to invoke additional calls to delete signers who are not part of the signing process via:
DELETE /api/packages/{package_id}/roles/{role_id}
To note:
-you'll receive the package ID in response of the first clone call
-make sure you are supplying role ID vs role Name. It's different from the signer name (Signer1, Signer2, Placeholder1, etc) you find in the UI, but normally in a format of UUID.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer