Changelog

The new POST /v3/document/detect_fields endpoint lets you analyze a PDF for form annotations or Dropbox Sign Text Tags before sending a signature request. It returns reusable form_fields_per_document and form_field_groups definitions together with structured warnings and errors.

The expires_at parameter now supports /signature_request/send_with_template, /signature_request/create_embedded_with_template, /signature_request/bulk_send_with_template, and /signature_request/bulk_create_embedded_with_template. /signature_request/update can also add an expiration to a request that did not previously have one. See the Signature Request Expiration Date guide.

Requests that use grouped_signers now reject duplicate email addresses, preventing ambiguous recipient assignments. Integrations that previously reused an address within grouped_signers must now provide unique email addresses.

Fixed embedded close events after a signer completes, declines, or reassigns a request. See the HelloSign Embedded SDK.

Fixed signer attachment processing so file-size and page-count limits are consistently enforced.

Fixed embedded signing so the original signer no longer receives a completion email after reassigning a request and the replacement signer completes it.

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.

Added documentation for the 409 Conflict response returned by the signature_request/update endpoint requests.

Increased the maximum recipient name length from 100 to 255 characters.

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 503 errors and a Microsoft add-in initialization race condition.