Skip to main content
A
Anonymous
December 21, 2025
Question

Does updating form fields in an agreement using API v6 endpoints send it out for signature?

  • December 21, 2025
  • 1 reply
  • 253 views

Hi,

We are building integrations with Adobe Sign API, and we wanted to understand the behavior on updating the form fields on a agreement in AUTHORING state.

We are following the below link to create an agreement with positioned signatures.
https://helpx.adobe.com/sign/kb/formfields-option-is-not-available-in-v6-of-rest-api-adobe-sign.html

We have one observation, that when we update the form fields with signature positions to an agreement in AUTHORING state, it automatically updates the agreement state and sends the agreement out for signature.
We did not find any such information in documentation, and wanted to ensure that this behavior is as expected.

Thanks,
Aditya


1 reply

Souvik Sadhu
Community Manager
Souvik SadhuCommunity Manager
Community Manager
December 22, 2025

Hi @46630497,

 

Hope you are doing well. Thanks for writing in!

 

To answer your question:

 

Yes — from the Acrobat Sign service’s perspective:

  • The purpose of AUTHORING state is to allow adding and adjusting fields

  • A signature field necessarily means the document is functionally complete

  • The system thus transitions automatically to the next applicable state (typically OUT_FOR_SIGNATURE)

You can refer to this article for more: https://adobe.ly/44Jq5uy

 

Please let us know if this helps or if you require further clarification.


Regards,
Souvik.

A
Anonymous
December 23, 2025

Thanks for the response Souvik.

We are facing one issue with this flow. When we call the formFields API to update signature fields, we are getting DOCUMENT_NOT_AVAILABLE.
The flow is same as what is described here
https://helpx.adobe.com/sign/kb/formfields-option-is-not-available-in-v6-of-rest-api-adobe-sign.html

1. Does it require any delay before we can make PUT formFields API call?
2. If yes, is there any recommended delay for above?
3. Is there any webhook event we can listen to, which ensures that a call to PUT formFields will work?

 

Souvik Sadhu
Community Manager
Souvik SadhuCommunity Manager
Community Manager
December 23, 2025

Thanks, @46630497, for the response.

 

Let me try and respond to your questions to the best of my abilities.

 

When you create an agreement in AUTHORING state, Acrobat Sign does not make the document immediately available for form-field authoring.

 

Behind the scenes, Adobe Sign performs several asynchronous steps after agreement creation:

  1. File upload and virus scan

  2. PDF normalization and conversion

  3. Internal page rendering

  4. Document indexing for form-field placement

Until these steps finish, the document exists but is not yet authorable, which causes: DOCUMENT_NOT_AVAILABLE

This is not a permissions issue or a bug, but a timing/state issue.

 

Now, coming to the questions:

 

1. Does it require any delay before we can make PUT formFields API call?

Yes! A delay is required. You cannot safely call: PUT /agreements/{agreementId}/formFields immediately after creating the agreement.

Even though the agreement ID exists, the agreement state is AUTHORING. The document may not yet be ready to accept form-field updates.

 

2. If yes, is there any recommended delay for the above?

I thoroughly reviewed all the documentation and could not find any official delay duration, as the processing time depends on factors such as file size, page count, PDF complexity, and backend load.

 

3. Is there any webhook event we can listen to, which ensures that a call to PUT formFields will work?

There is no webhook for “document ready for form fields.” This is an important limitation, as webhooks are available for various agreement lifecycle events (e.g., CREATED, SENT, SIGNED, etc.).

There is no webhook for “Document processed”, “Authoring assets ready”, and “FormFields API is now available”.

 

Hope this helps.


Regards,
Souvik.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices