← Back to all sparks
D

Dropbox Sign

COLLAB
Velocity5.0

Electronic signature and document workflow platform, formerly HelloSign

Dropbox Sign's changelog has slowed to a trickle of API limits and field notes.

e-signatureapideveloper-toolingdocumentationmobile-webmaintenance
Current state
Dropbox Sign is an e-signature service sold primarily through its API, and this feed is the developer changelog rather than a product one. Activity is sparse: two entries in 2026 to date, both small — a validation-bypass flag for text tag extraction, and a raised ceiling of 100 files per signature request. The one substantive item is older, a redesigned mobile web signing experience being rolled out gradually to API plans starting with Essentials.
Where it's heading
What is visible here is a mature API in maintenance: limits raised when customers hit them, response fields added when integrators need to branch on them, documentation corrected when it misleads. The signer app redesign is the only entry that touches what an end user sees, and it has been rolling out slowly since January rather than shipping as a release. Nothing in this feed suggests a change of direction.
Prediction
The Signer App rollout is the only open thread with a stated plan — expansion beyond Essentials API plans is the most likely next entry, though this changelog is too sparse to read a roadmap from.

Recent moves

  1. 14d ago

    Flag to bypass text tag extraction errors

    A flag that lets signature request, template and unclaimed draft workflows proceed past text tag extraction validation errors. Narrow, but it unblocks integrators generating documents whose tags do not always parse cleanly.

    View source ↗
  2. 1mo ago

    Signature requests now accept up to 100 files

    The default cap on files per signature-request submission rises to 100. A limit raise of the kind that shows up when larger document packages start hitting the ceiling.

    View source ↗
  3. 7mo ago

    Redesigned mobile web signer app begins rollout

    A redesigned mobile web signing experience beginning a gradual rollout to API plans, starting with Essentials. The only entry in this feed that changes what a signer actually sees, and it is being released slowly enough that customers must ask support about their own timing.

    View source ↗
  4. 1y ago

    Fax status and error codes documented

    Fax status and error codes added to the documentation. Reference material for an existing capability, with no change to behaviour.

    View source ↗
  5. 1y ago

    is_signed field added to signature request responses

    An is_signed boolean on the Signature Request response indicating whether a signature or initials field was completed, with an accompanying SDK bump. Small, but it saves integrators inferring completion from other fields.

    View source ↗
  6. 1y ago

    SDK license banner and OAuth bearer format correction

    An MIT license banner on the SDK page and a correction removing incorrect references to JWT as the OAuth bearer format. Documentation accuracy work with no functional change.

    View source ↗