When creating agreement using API I always get agreement was automatically canceled

[sp_omer]

After uploading file through REST API documentation transientId works ok, I'm able to use it to create agreement. But when uplaoding file through my request implementation transientId I receive makes agreement creation cancelled.

Somehow it looks like file is not created in second case, but transientId is issued without problem.

Why are my agreements cancelled when getting transientId through python requests.POST, and it is ok when receiving it through REST API documentation examples?

EDIT:

Have fixed it with boundary changes (added File-Name Content-Type in multipart + appliccation/pdf Content-Type inside multipart boundary for file just before file content). Hope it helps someone else.

[Emanuele Reds]

Finally! thanks a lot, u saved me.. i was struggling with the same issue for days and i was about to give up

[Viswa362004619xl8]

Thank you so much, I have been work around with this error for two days. Finally i got it.

[MeenakshiNegi]

Hi Viswa362004619xl8,

Thank you for reaching out.

Glad to know the information shared in the initial post resolved the issue. 

EDIT:

Have fixed it with boundary changes (added File-Name Content-Type in multipart + application/pdf Content-Type inside multipart boundary for file just before file content). Hope it helps someone else.

If you are using the Acrobat Sign enterprise plan and need any help with integration, the experts can best answer it. Please contact our Adobe Sign Enterprise support team for the correct information. You may contact them using the steps in the following help document: https://adobe.ly/3U1HUzV.

Refer to the following help document for more information on Acrobat Sign Integration: https://adobe.ly/43I2jgK.

Thanks,

Meenakshi

Marking a reply or response “Correct” will help future users with the same issue quickly identify the correct answer.