Agreement Auto-Sending, Ignoring Custom Signature Fields, and Webhook Functionality

[dolapo_8706]

Hello Adobe Acrobat Sign Community,

I’m integrating Adobe Acrobat Sign with a custom workflow and running into multiple roadblocks:

1. Agreements Auto-Sending

•Goal: I want to create an agreement in an “AUTHORING” or “DRAFT” state, add my custom fields (including signature fields), and only then explicitly send it out.

•Issue: As soon as I use the PUT /agreements/{agreementId}/formFields endpoint to add custom fields, the agreement automatically transitions to “OUT_FOR_SIGNATURE” and is sent to the signer, even though I never manually changed its state to “IN_PROCESS.”

Question:

How can I keep an agreement in a non-sent state until I explicitly trigger sending? Is there a way to prevent Acrobat Sign from auto-sending upon form-field updates?

2. Custom Signature Fields Overridden

•Goal: I want to define my own signature or initials fields at specific locations in the PDF (via the PUT /agreements/{agreementId}/formFields call).

•Issue: Acrobat Sign often replaces/ignores my custom signature fields and inserts a default signature block in a different location. In some cases, the custom fields appear, but the signer also sees an automatically generated signature block they must complete instead.

Question:

How can I ensure that only my custom signature fields appear, and Acrobat Sign doesn’t override them with an auto-generated signature block?

3. Webhook Not Firing on “Agreement Signed”

•Goal: I want to receive a webhook notification when an agreement is fully signed. I set up a webhook (via the Acrobat Sign admin UI) for certain events, such as “AGREEMENT CREATED,” “AGREEMENT MODIFIED,” etc.

•Issue: I receive a notification for “Agreement Viewed,” but never see a notification when the signer completes the signing. I don’t see a dedicated “Agreement Signed” event in the dropdown list, and the existing events do not appear to capture a successful signature event.

Questions:

1.Which event or combination of events in the webhook configuration will reliably indicate that an agreement has been signed by all parties?

2.Are there recommended best practices to detect “Agreement Signed” or “Signing Complete” via webhooks?

Example Workflow

1. POST /agreements with "state": "AUTHORING".

2. PUT /agreements/{agreementId}/formFields to add custom signature fields.

3.(Unexpectedly, the agreement transitions to “OUT_FOR_SIGNATURE” and includes a default signature block.)

4.Webhook: I receive notifications for “Agreement Viewed,” but not for “Agreement Signed.”

What I’ve Tried

•Setting "state": "AUTHORING" in the creation payload.

•Attempting to manipulate participant sets or remove auto signature blocks.

•Reviewing the available webhook events (AGREEMENT CREATED, AGREEMENT MODIFIED, etc.) for a “signed” equivalent.

Any insights on preventing automatic sending, forcing only custom signature fields, or capturing a “signed” event via webhook would be greatly appreciated -

If you need specific code snippets, request/response JSON, or logs, I’m happy to provide them. Thank you in advance for your help.

[Meenakshi Negi]

Hi dolapo_8706,

Thank you for reaching out.

We have checked that you are using the Acrobat Sign Developer service, so we are 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/41eTZEs. You may use the Contact Us button for Adobe Sign Solutions under the team tab.

Thanks,

Meenakshi

[dolapo_8706]

Hi @Meenakshi Negi -  thank you for the response. 

That link did not work. Is there a specific channel I can reach out to? 

Thank you