API documentation
- Added
ignore_text_tags_extraction_errorsto the API reference for supported signature request, template, and unclaimed draft workflows. Set this field totrueto ignore validation errors from text tag extraction.
Features
- Increased the default maximum number of files accepted per signature-request submission to 100.
Fixes
-
Improved error handling in the Ruby SDK.
-
Improved OAuth error handling for authorization callbacks and scope validation.
-
Improved handling of expired or invalid signing links by showing a clear “Nothing to sign” page.
-
Resolved an issue that could leave document-deletion jobs stuck.
Fixes
-
API error names remain strings to preserve compatibility with existing SDK integrations.
-
Improved audit-trail IP address retention for bulk-send and expired requests.
-
Improved OneDrive setup retry handling.
-
Resolved OIDC
503errors and a Microsoft add-in initialization race condition.
Announcements
- New Signer App: A rollout of the redesigned mobile web signing experience has begun for API plans and will be gradually rolled out over time. Please submit a ticket to our support team for an inquires regarding this rollout. Rollout for API plans will start with the Essentials API plans.
Features
- Salesforce Integration - SMS delivery/signer verification: Sign for Salesforce now supports SMS request delivery and signer verification, enabling faster document turnaround and secure signer access directly within Salesforce workflows. Learn more in the Sign for Salesforce FAQs.
Announcements
- New Signer App: A redesigned mobile web signing experience is now available, introducing Form View for focused field completion and Drawer Flow for an app-like document experience — both optimized for mobile without zooming. See the Form View Help Center article and the Signer App API updates documentation. Not supported for legacy Sign ENT / ENT+ plans. For Sign free accounts, UI Essentials, Standard, and Premium.
Announcements
- Data Residency: Global Data Residency is now available, allowing teams under a single subscription to configure distinct document data residency settings to meet regional compliance requirements. See the Dropbox Sign Data Residency overview. Available for Sign Web App and API Premium plans. Not supported for legacy Sign ENT / ENT+ plans.
Features
- SMS Activity Report: New Sign SMS Activity Report available. This report gives Admins visibility into SMS request usage and performance, helping teams monitor activity and optimize SMS add-on usage. Available for Sign Web App and API Standard and Premium plans. Not supported for legacy Sign ENT / ENT+ plans.
- Multiple App Domains: API apps now support up to 10 domains per configuration, simplifying multi-platform integrations and reducing maintenance overhead. Available for Sign API Premium plans. Not supported for legacy Sign ENT+ plans.
Features
- Saved Signatures: Embedded signing now supports Saved Signatures, allowing returning signers to reuse a previously saved signature during the embedded flow. See the Embedded Saved Signatures API documentation for details. Available for Sign API Standard and Premium plans. Not supported for legacy Sign ENT / ENT+ plans.
Features
- Added saved signature feature to embedded signature requests. See Embedded Saved Signatures documentation to enable this feature.
Documentation Improvements
- Added list of possible Fax status and error codes to Fax documentation.
Features
- Signature Types section added with a NOM 151 Overview and how to sign with NOM 151.
Documentation Improvements
- Updated documentation to reflect API app Self Publish documentation.
Features
- Dropbox Fax API endpoints are now live and can be used in test mode or with a paid Fax API subscription.
November 27, 2024
- Added boolean property
is_signedto Signature Request response to indicate if asignatureorinitialsfield was signed. - SDK version update.
September 30, 2024
- Added SDK MIT license attention banner on Official Dropbox Sign SDKs page.
- Removed all references of JWT as the bearer format for OAuth access tokens. Bearer format is not JWT, but a base64 encoded string.