I POST to api/rest/v6/agreements to create my agreement (with state: AUTHORING)
A GET from api/rest/v6/agreements shows all is well.
Then i get the participant set IDs and use this information to PUT my formFields api/rest/v6/agreements/{agreementId}/formFields.
However this last step changes the agreement status to OUT_FOR_SIGNATURE
( I was hoping i could set the status to IN_PROCESS using api/rest/v6/agreements/{agreementId}/state ... but this API call fails with a 403 status OPERATION_NOT_ALLOWED )
Is there an account setting that causes this unexpected behaviour? i don't use workflows.
Many thanks!
Copy link to clipboard
Copied
Hi there,
We have checked that you are using the Acrobat Sign trial service. If you have a question related to API integration, the experts can best answer it.
You may also contact the pre-sales team. They will be able to provide you the pre-sales technical assistance and share the correct information. Please refer to the following link to contact them: https://acrobat.adobe.com/us/en/sign/pricing/plans.html. You may use the Contact Us button for Adobe Sign Solutions under the team tab.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Hey, have you sorted it out? Maybe you have some hints? (because the same issue)
Copy link to clipboard
Copied
Thank you for reaching out.
We have checked that you are using the Acrobat Sign Developer service and hence moving this thread to the Acrobat Sign Developer board for visibility.
If you have a question related to API integration, the experts can best answer it. With the developer account, you may also contact the pre-sales team. They will be able to provide you the pre-sales technical assistance and share the correct information.
Please refer to the following link to contact them: https://adobe.ly/4eOYpae. You may use the Contact Us button for Adobe Sign Solutions under the team tab.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Late reply but I've just been going through similar pain, so posting here so it's available to anyone else who lands here.
It seems that settings the form fields triggers the sending of the agreement. I personally regard this as bad practice, especially since it's not documented! This appears to be the only way it works - I've not seen any settings that change it. I suggest you make the FormFields call the last as it also sends.