I followed the above guide . But even though i get 200 ok response to /api/packages/{packageId}/documents/signed_documents, i am not seeing documents signed.
Note : i have use position extraction to create a package.
Could you share a package ID you were testing? And if possible could you also share the code snippets without sensitive information, where you implemented the three steps to bulk sign -- (1)get signer authentication token (2)use authentication token to get a session ID (3)use signer session ID as cookie header to invoke bulk sign API?
In terms of the position extraction, I won't think it's the cause of the issue because OneSpan Sign system processes all documents the same no matter how you designed them. (x/y coordinates, via designer page, or automatic extraction methods)
Reply to: signing on behalf of signer
Friday, May 8, 2020 at 12:11pmHi nareshishere,
Bulk Sign feature enables you to sign all documents on behalf of a signer in a single call, go check the guide here.
Duo
Reply to: signing on behalf of signer
Friday, May 8, 2020 at 03:52pmHi Duo,
I followed the above guide . But even though i get 200 ok response to /api/packages/{packageId}/documents/signed_documents, i am not seeing documents signed.
Note : i have use position extraction to create a package.
Thanks
Naresh S
Reply to: signing on behalf of signer
Monday, May 11, 2020 at 08:43amHi Naresh,
Could you share a package ID you were testing? And if possible could you also share the code snippets without sensitive information, where you implemented the three steps to bulk sign -- (1)get signer authentication token (2)use authentication token to get a session ID (3)use signer session ID as cookie header to invoke bulk sign API?
In terms of the position extraction, I won't think it's the cause of the issue because OneSpan Sign system processes all documents the same no matter how you designed them. (x/y coordinates, via designer page, or automatic extraction methods)
Duo
Reply to: signing on behalf of signer
Monday, May 11, 2020 at 04:51pmIts working now thanks, There was a required field in the document which was giving error.