Our Community is in read-only mode until April 8th, learn more here. You can still search existing threads or get help via Dropbox Support, the Dropbox Help Center, or Learn.
Group Content
Note from the Dropbox Team
Our Community is in read-only mode until April 8th, learn more here. You can still search existing threads or get help via Dropbox Support, the Dropbox Help Center, or Learn.
We're making some changes to the Dropbox Community
Hi everyone, Over the past few years, Community members have shared feedback, ideas, and questions that help shape how this community supports you. We’ve been listening closely, and as a result, we’ll soon be moving the Dropbox Community to a new platform designed to deliver a better, more seamless experience. 😍 We’re just a few days away from launching an updated Dropbox Community experience, and we wanted to help you feel ready for what’s coming. To facilitate this move, the Dropbox Community Forum will be available as read-only from Monday, March 30, through Wednesday, April 8. This means that you will not be able to start new discussions, reply to threads, like posts, accept solutions or add or vote for ideas for one week. You will still be able to read discussions and find solutions during this time. Here’s what to know ahead of the move: This update is all about improving usability, performance, and helping you to get the answers you need. In addition to some tweaks to make the experience easier to use, we also are moving to a new home on community.dropbox.com. The heart of the Dropbox Community isn’t changing - we’re still here to help and you’ll continue to be able to connect, learn, and get help from fellow community members, experts and our product teams. Some sections, buttons and settings might have moved around or work slightly differently, but everything should still be here, so let us know if you can’t find something or it’s not working as you expect! Thanks for your flexibility as we take this next step together. We’re excited to continue building a space that’s helpful, welcoming, and easy to use. Thank you for being part of what makes the Dropbox Community special. Stay tuned for more updates as construction gets underway! 👷 ~ Angie25Views0likes0CommentsMultiple 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.90Views0likes0CommentsEmbedded 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?452Views0likes6CommentsSetting 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?256Views0likes1CommentTemplate Created callback does not contain metadata for Date signed field type
We use embedded templates in our web app to create templates. However, when we receive the callback in our Java application, the TemplateResponseDocumentFormFieldDateSigned object does not include metadata values such as font family, font size, and date format. Secondly, when we create a signature request using the SubFormFieldsPerDocumentDateSigned object, we notice that only the font_family and font_size properties are implemented, while the date format is missing. When creating a "Date Signed" field in the embedded template editor, we can set the font family, font size, and date format. Why aren't these values included in the template creation callback? Additionally, why is the date format missing when manually creating the fields for a signature request?Solved358Views0likes4CommentsMissing 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);878Views0likes17Comments[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)1.1KViews0likes3CommentsWhat 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!958Views1like0CommentsInvalid_Grant whlie generating Access Token using saved Refresh token in Dropbox Sign .NET SDK
Hello Greg-DB , I am using the following Dropbox Sign .NET SDK code in my project to generate Dropbox Sign Access token using previously saved Refresh token. public async Task<TokenResponse> GetRefreshToken(TokenResponse tokenResponse) { TokenResponse tokenResponse2 = new TokenResponse(); string errorlog = ConfigurationManager2.AppSettings("ErrorLog"); var config = new Configuration(); var oAuthApi = new OAuthApi(config); try { var data = new OAuthTokenRefreshRequest(refreshToken: tokenResponse.RefreshToken); var result = await oAuthApi.OauthTokenRefreshAsync(data); if (result != null) { tokenResponse2.Expires = result.ExpiresIn; tokenResponse2.AcquireTime = DateTime.Now; tokenResponse2.AccessToken = result.AccessToken; tokenResponse2.RefreshToken = result.RefreshToken; tokenResponse2.AcquireTime = DateTime.UtcNow; } return tokenResponse2; } catch (ApiException ex) { File.AppendAllText(errorlog, "\r\n\r\n" + "nGetRefreshToken: - Error"); File.AppendAllText(errorlog, "\r\nException when calling Dropbox Sign API: " + ex.Message); File.AppendAllText(errorlog, "\r\nStatus Code: " + ex.ErrorCode); File.AppendAllText(errorlog, "\r\nStack Trace: " + ex.StackTrace); throw ex; } catch (Exception ex) { File.AppendAllText(errorlog, "\r\nGetRefreshToken - Error"); File.AppendAllText(errorlog, "\r\n" + ex.Message + "\r\n" + ex.StackTrace); } return tokenResponse; } I am getting the following Error Message and Stack Trace. Error converting value "invalid_grant" to type 'Dropbox.Sign.Model.ErrorResponseError'. Path 'error', line 1, position 24. at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader, Object value, CultureInfo culture, JsonContract contract, Type targetType) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent) at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType) at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings) at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings) at Dropbox.Sign.Client.Configuration.<>c.<.cctor>b__78_0(String methodName, IApiResponse response) at Dropbox.Sign.Api.OAuthApi.OauthTokenRefreshWithHttpInfoAsync(OAuthTokenRefreshRequest oAuthTokenRefreshRequest, Int32 operationIndex, CancellationToken cancellationToken) at Dropbox.Sign.Api.OAuthApi.OauthTokenRefreshAsync(OAuthTokenRefreshRequest oAuthTokenRefreshRequest, Int32 operationIndex, CancellationToken cancellationToken) at SGCloudMigration.Business.DropboxSignUtility.GetRefreshToken(TokenResponse tokenResponse, String relationshipname) in D:\SG Cloud Migration\SGCloudMigration.Business.Core\DropboxSignUtility.cs:line 364 Please help. Thanks, GaganSolved2.3KViews0likes2CommentsWelcome 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.3.4KViews4likes0Comments
About Dropbox Sign API
This is a space for developers to get information and support for the Dropbox Sign API. Find answers to your questions, troubleshoot issues, and connect with others building with the Dropbox Sign API. Latest Activity: 5 days ago
Open Group
The Dropbox Community team is active Monday to Friday. We try to respond to you as quickly as we can, at least within a business day.
If your request is urgent, please be sure to Contact Support so our Customer Experience team can get started on your request.
This community group is for networking and collaboration, not contract discussions. Reach out to your account team for questions you need answered about your specific account and contract.