nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can you update a Signer with an Email Address that's already been used by a previous Signer?

Jeff_Capp

I'm currently migrating from HelloSign to Dropbox Sign and have encountered error that I did not experience with HelloSign.

My main question is: Can a signer be updated with an email address that has already been used by another signer who completed signing on the same signature request?

For example, say a signature request has two signers:

Signer 1 has the email Signer1@email.com and completes signing.
I then try to update Signer 2 to also use Signer1@email.com.
The update to Signer 2 fails.

My initial testing indicates that reusing the same email address causes the update to fail. If I update Signer 2 with a different email address, it works successfully.

This is an important use case for us because over half of our submitted forms require more than one signer, and in some cases the same person needs to sign for multiple roles on the same form.

I'm trying to determine whether this is an intentional restriction in Dropbox Sign that differs from the previous HelloSign behavior, or if this could potentially be a bug.

For additional context, we use templates with multiple signers, Embedded Signing, and the Dropbox Sign .NET NuGet package.

Find more posts tagged with

API

Comments

Aleppoo

Hi Jeff,

Dropbox Sign documentation does appear to support multiple signers sharing the same email address, and I couldn’t find a documented restriction preventing an email update to an address already used by another signer.

Could you share the exact error message you’re receiving when the update fails?

Jeff_Capp

Hi Thanks for the quick response. I found this in the logs.

Dropbox.Sign.Client.ApiException: Error calling SignatureRequestUpdate: {"error":{"error_msg":"Unable to update signature request - Unable to update signature id to '050fa241f7ce242f6f3e79d0ed66c66d' for tsm 1327965679, it already exists","error_name":"bad_request"}}

I can dive further into it to find more information. But initially this is what I have.

Jeff_Capp

I was able to find the signature request from the app callback. I striped away some of the important details so I don't expose sensitive data. But the signatureRequestId and SignatureIds are real
{
"signature_request": {
"signature_request_id": "e0173d8599557b2e63759461685535e6207dff04",
"title": "Instruction Form",
"is_complete": false,
"is_declined": false,
"has_error": false,
"signatures": [
{
"signature_id": "050fa241f7ce242f6f3e79d0ed66c66d",
"signer_email_address": "user@example.com",
"signer_name": "Signer 1",
"signer_role": "customer",
"status_code": "signed"
},
{
"signature_id": "6ee5ea3028e9cd3181e5938326c56307",
"signer_email_address": "placeholder@example.com",
"signer_name": "Signer 2",
"signer_role": "Broker",
"status_code": "awaiting_signature"
}
]
},
"event": {
"event_type": "signature_request_viewed",
"event_metadata": {
"related_signature_id": "6ee5ea3028e9cd3181e5938326c56307"
}
}
}

Aleppoo

Thanks Jeff, this helps. The signature_id reported as “already exists” is exactly Signer 1’s ID, so this looks specific to updating Signer 2 to the email of an already-signed signer.

This may be an edge case or bug worth confirming with the Dropbox Sign team.

Jeff_Capp

Thank you! Like my post says once I use a different email such as a personal one it worked fine. Fro context I'm using Dropbox.sign version 2.4.0 nuget package. Let me know if I can provide anymore helpful details.