Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Group Content
Pinned Post
Multiple Signers: Both Embedded + Non-Embedded workflows?
Hello. Is it possible to create a multi-signer signature request where: Signer 1 uses the "embedded" signature flow Signer 2 uses the "non-embedded" signature flow I've gone through both the "embedded" and "non-embedded" workflows (in API docs) separately, but I'm unclear how I could combine these two flows for a multi-signer signature request. My use case is that Signer 1 is a user of my app, but Signer 2 is not. Signer 1 can requests signatures on a document that both Signer 1 and Signer 2 need to sign. Since Signer 1 is a user of my app, I can push them through the embedded signing flow, whereas Signer 2 would need to go through the Dropbox Sign UI flow (non-embedded) from the email link. Thanks.
Embedded request - requester_email_address can be a mail that not relate to a user?
Question or Issue I am a company that wants to send a request a signature embedded in my website, but the requester_email_address should be each request a different email for each request, but it should be under the same company. How can I do it without opening a user account for all my users?
Setting expiry date with create_embedded_with_template
Hi, we want to start using the auto expiration feature on Dropbox sign but for some reason the /unclaimed_draft/create_embedded_with_template endpoint does not include the parameter for this setting. We noted that the template endpoint is not one of the listed endpoint on the expiration feature page. Question 1: Will this be added at some stage, or will we need to handle expirations on template linked signature requests manually? Question 2: Is it best practice on Dropbox Sign to not use templates?
Missing parameter: client_id for lwc
Im working on a lwc where id like to embed a signing process in iframe, I was able to successfully retrieve sign URL, but when I try to use it on iframe I got following error, at which step do I need to set my client id? So far I used this with client id in request body String apiUrl = 'https://api.hellosign.com/v3/signature_request/create_embedded_with_template'; and request.setEndpoint('https://api.hellosign.com/v3/embedded/sign_url/' + signatureId); with just signature id in request body Also I have a problem setting body for my request, I used this class to generate json string, but when I use this approach I get error({"error":{"error_msg":"No template_id or template_ids specified","error_path":"template_id","error_name":"bad_request"}}) HelloSignJSON.Signing_options so = new HelloSignJSON.Signing_options(); so.default_type = 'draw'; so.draw = true; so.phone = true; so.type = true; so.upload = true; HelloSignJSON.Signers signer = new HelloSignJSON.Signers(); signer.role = 'Lead.Customer'; signer.name = 'Rostyslav'; signer.email_address = 'popov.rst@gmail.com'; List<HelloSignJSON.Signers> signers = new List<HelloSignJSON.Signers>{signer}; HelloSignJSON hsj = new HelloSignJSON(); hsj.template_ids = new List<String>{'90c43afee504f24a2dcd67ab7991f8f3f5900ef3'}; hsj.client_id = 'CLIENT_ID'; hsj.subject = 'Embedded Subject'; hsj.message = 'Embedded message'; hsj.signing_options = so; hsj.test_mode = true; hsj.signers = signers; String requestBody = JSON.serialize(hsj);[Dropbox Sign API] What is a best way to identify each document with their template after download
Hi, I have integration with Dropbox Sign API (earlier HelloSign) that downloads documents after they were signed. I am downloading a zip file, and I would like to save them with different names based on the template they were created with. Is there a way to identify which documents were created from which template? (Right now, I am using the template ids array, which comes with the 'signature_request_all_signed' event, and assuming that each file in the zip file will be in the same order as id in template ids array)
What to include in a Support Ticket Request
Hey Sign API Community! We're glad to see your engagement and activity after opening up this space! If you do find that you need to write into our support team, we wanted to highlight some helpful pieces of information that our team needs to investigate your issue. Please submit a request from the primary email address associated with your account and include the following if applicable: Error / description of issue Signature request ID (aka Document ID) and/or Template ID for affected request API Endpoints & SDK version you are using in your workflow (i.e. /v3/signature_request/create_embedded etc.) Any screenshots, recordings, and applicable code snippets are also extremely helpful in our investigations. We look forward to assisting you with your Sign API integration!
Welcome to the Sign API Developer Community
We're excited to introduce the Sign API Developer community, a space for you to engage with everything related to the Sign API. This forum is where you can ask questions, share knowledge, and collaborate to get the most out of Sign API. Whether you're an experienced developer or just starting with the Sign API, this forum is your go-to resource for technical exchange. Who should join? The forum is open to all, especially developers and technical users of the Sign API. If you have insights to share, questions to ask, or are looking to enhance your understanding of the Sign API, this community is for you. How to leverage this Community forum We encourage you to: Discuss: Engage in technical discussions, ask questions, and provide answers. Share: Contribute your knowledge, share your use cases, and explore new ways to use the Sign API. Feedback: Offer suggestions for improvements or new features, or bugs that need to be addressed. Tell us what you think We’d love to hear your thoughts on the Sign API community, so please leave any feedback in the comments below.
About Dropbox Sign API
This is a space for developers to get information on the Dropbox Sign API, share ideas with each other and receive support on Dropbox Sign API.
Open Group