User Guide Cancel

Technical notifications

 

Adobe Acrobat Sign Guide

What's New

Get Started

Administer

Send, Sign, and Manage Agreements

Advanced Agreement Capabilities and Workflows

Integrate with other products

Acrobat Sign Developer

Support and Troubleshooting

Review the Technical Notifications listed and bookmark the ones that are important to you.

Tip:

The Technical Notifications page is updated regularly with new information, making its content highly dynamic. While localized versions are available, the translation process may cause slight differences from the authoritative US English version. Always refer first to the US English page for the most accurate and up-to-date information.

[Next Release] The next Adobe Acrobat Sign release is scheduled for April 22, 2025

Feature Release: Adobe Acrobat Sign – March 17th Release Completed

The release was completed to all shards with no downtime to any services.

Current Notices:

New items are added to the table as they are reported. The full list is resorted at the beginning of the month.

Status

Issue or Event

Execution Date

Imminent

Important

March 1, 2025

Imminent

April 22, 2025

Imminent

April 22, 2025

Imminent

April 22, 2025

Imminent

April 22, 2025

New

Imminent

April 22, 2025

New

Imminent

April 22, 2025

Updated

Important

July, 2025

New

Current

New

May 20, 2025

Pending 

July 22, 2025

Pending 

July 22, 2025

Pending 

Q2, 2025

Pending 

December 1, 2025

Informational

Current


Disablement of the SOAP API for Adobe Acrobat Sign Embedded Partners has been scheduled for March 1, 2025

First Reported: June 2018 - Updated May 2024

Current

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.


Disablement of the SOAP API from Adobe Acrobat Sign accounts is scheduled to start in February 2024

First Reported: June 2018 - Updated May 2024

Current

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.


The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload. 
Sandbox is to be updated in the June 2025 release.
Production is to be updated in the July 2025 release.

First Reported: September 2024 - Updated April 2025

Current 

The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads.
The Sandbox environment will be updated in the June release.
The Production environments will be updated in the July 2025 release.

The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload. 

 

The new Request Signature environment will be promoted to be the default experience and the switch links between Classic and Modern environments will be removed in the April 2025 release.

Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

This update only applies to the Send (Request e-signatures) page. Structured Self-signing workflows are not yet included.

First Reported: March 2024 - Updated January 2025

Current 


The modern Send in Bulk environment will become the default experience for all commercial accounts in April 2025.
Switch links will remain available.

First Reported: March 2024 - Updated February 2025

Current 

Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.


Updated Create Template Experience Coming in April 2025

First Reported: February 2025

Current 


The Account tab will be renamed to Admin starting with the April 2025 release

First Reported: February 2025

Current 


Adobe Acrobat Sign: Improved user onboarding.

First Reported: March 2025

Current 


New Webhook limits for Developer tier accounts

First Reported: March 2025

Current 


Adobe Acrobat Sign Webhook service available for status event subscriptions.

First Reported: March 2025

Current 


REST API GET /agreements Optimizations

First Reported: March 2025

Current 


The classic Compose page will be retired and removed from the commercial interface in the July 2025 release.

Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

First Reported: June 2024 - Updated January 2025

Current 


The classic Send in Bulk environment will be removed from service in July 2025.

First Reported: March 2024 - Updated February 2025

Current 

Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.


Classic reporting to be removed from service in the first half of 2025

First Reported: September 2022 - Updated March 2024

Current 


Deprecation of the Adobe Acrobat Sign REST API v1-v4.
End of support and removal of legacy REST API versions on December 1, 2025.

First Reported: September 2024

Current 

Action Required

All customers using the API must update their APIs to utilize the version 6 endpoints as soon as possible to ensure uninterrupted availability. 


External source drives to be removed from support in the new Request Signature experience

First Reported: May 2024

Current 


Additional Resources


Adobe Acrobat Sign SSL Certificate updates in January, 2025

First Reported: December 2024

Removed from Current list: February 2025

Adobe Acrobat Sign will rotate the Adobe Acrobat Sign SSL Certificate on January 22, 2025.

In addition, a new SSL certificate is being deployed to support the WAF network changes being made in January 2025This new certificate directly impacts access to the Acrobat Sign service and must be installed before the WAF goes online.

Action Required

  • Every customer account that explicitly secures network activity must include the new WAF SSL certificate in its list of stored certificates.
  • If you have custom-built integrations with Acrobat Sign using either the SOAP or REST APIs and if any of these integrations have ‘pinned’ the existing public key, no other action is required.
  • If you are using Acrobat Sign’s SSL certificates for SSO, or if you’re pinning the certificate itself (or using other methods), you can find the new Acrobat Sign SSL certificates in the Adobe Acrobat Sign System Requirements.
    • If your SSO configuration supports multiple public certs/chains, you can add the new certificates now and remove the old public cert/chain from your configuration after the January switch.
    • If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on January 22, 2025.  

The new SSL certificates will be active on January 22, 2025.


Customers with a Sandbox environment will be able to access the new Recipient experiences the first week of December 2024

First Reported: November 2024

Removed from Current list: February 2025

The new recipient experience contains signing improvements for both desktop and mobile web browsers. This new experience is being rolled out over the first months of 2025 but will be available in the Sandbox environment in the first week of December 2024.


The Accept-Charset header will be removed from Webhook and Callback notifications in the November 2024 release

First Reported: August 2024

Removed from Current list: January 2025


Adobe Acrobat Sign Cookie Partitioning to be enabled in the November 2024 release.
Available in the Sandbox now.

First Reported: September 2024

Removed from Current list: January 2025


Custom Workflow Designer places a 100-character limit on labels for all new and existing workflow templates

First Reported: November 2024

Removed from Current list: January 2025

With the November 2024 release, the editable labels in the Custom Workflow Designer have been limited to 100 characters. This limit is evaluated when the workflow is created or updated.

Preexisting workflows that have labels over 100 characters can still be sent successfully, but if the workflow is updated, the label must be reduced to 100 characters or less before it can be saved. Offending labels are outlined in red for easy discovery.

New workflows will warn about the label limit before they are saved.

Action Required

It is recommended that admins with control over custom workflows open and review each workflow to ensure that they don't have errors on their template.

Archived Notifications

Listed by the date when the notice was removed from the current notice list, most recent to oldest.

Get help faster and easier

New user?