Skip to main content
  • EN

I am using the create sign request API with the following body to create a sign request:



{


    "external_id": "10000",


    "parent_folder": {


        "id": "0",


        "type": "folder"


    },


    "signers": [


        {


            "role": "signer",


            "email": "ben.jessup@oasisdigital.com"


        },


        {


            "role": "approver",


            "email": "benjamin.jessup@valiantys.com"


        }


    ],


    "source_files": [


        {


            "id": "1056087946155",


            "type": "file"


        }


    ]


}


After signing and approving the request it goes into a “finalizing” state (shown as “In Progress” in the UI), then eventually goes into a “error_finalizing” status.



Initially I encountered this in a Atlassian Connect Express application, but I saw the same behavior after using Postman to create the sign request. Any thoughts on what could be causing this error? Is there any way to see more detail on the error?

Hi @benjessupoasis , welcome to the forum!



Help me replicate this.



From above it seems a simple request…



Any other details we should know about?



Cheers

I am attempting to create a new sign request using as little information as possible - in this example I am just passing a file to be signed and the signer/approver, as well as an external ID for automation purposes.



I tried creating the request with the following body and this worked as intended (after signing, the request was completed rather than being stuck in finalizing and then erroring).



{


    "external_id": "10000",


    "parent_folder": {


        "id": "206115788143",


        "type": "folder"


    },


    "signers": [


        {


            "role": "signer",


            "email": "ben.jessup@oasisdigital.com"


        }


    ],


    "template_id": "d996578e-a72e-4559-8c28-dae743465195",


    "source_files": []


}


It seems like using a template should be required, or perhaps something else should be required when trying to create a sign request based on a source file rather than a template.

Hi @benjessupoasis ,



Interesting, I’ll investigate, and try to replicate the error.



What is puzzling to be is that the signature process is giving an error at the very end, I wonder if it can write on the root folder of the user who requested the signature.



Are there any more details on the error message/notification?



Cheers

I tried my original request again with a different parent folder specified instead of the root, and now the problem is resolved. After signing the request it completes as expected.



Weird bug, thank you for the quick reply!

Awesome, I’ll ping the engineers about this anyway, see what they have to say.



But for now I think we found a workaround, assuming this won’t be a problem fo ryour use case.



Cheers

Reply


Terms & ConditionsCookie settings