We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
API
9 TopicsMissing 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);35Views0likes0CommentsWelcome 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.3KViews4likes0Comments[Dropbox Sign API] Support for text tags in templates
I'd like to use text tags in templates. The documenation seems to imply this is possible (e.g. https://developers.hellosign.com/docs/signature-request/walkthrough/mentions text tags right after a section on templates) but `use_text_tags` is not supported as a parameter for the `/signature_request/send_with_template` endpoint. Is it possible to use text tags with a template?Solved2.7KViews0likes5CommentsError during send signature request - Email not valid
I'm trying to send a signature request via Java client this is my code (written in Kotlin) : class DropBoxSigner { companion object { private val apiClient = Configuration.getDefaultApiClient() .setPassword("api token") } fun sign() { val signatureRequestApi = SignatureRequestApi(apiClient) val signer1 = SubSignatureRequestSigner() .emailAddress("test.user1@dove.it") .name("Test User1") .order(0) val signer2 = SubSignatureRequestSigner() .emailAddress("test.user1@dove.it") .name("Test User2") .order(1) val signingOptions = SubSigningOptions() .draw(true) .type(true) .upload(true) .phone(true) .defaultType(DRAW) val data = SignatureRequestSendRequest() .title("a title") .subject("Request subject") .message("Request message") .signers(listOf(signer1, signer2)) .addFilesItem(File("./dropbox-sign.pdf")) .signingOptions(signingOptions) .testMode(true) try { val result = signatureRequestApi.signatureRequestSend(data) println(result) } catch (e: ApiException) { System.err.println("Exception when calling SignatureRequestSendRequest") System.err.println("Status code: " + e.code) System.err.println("Reason: " + e.responseBody) System.err.println("Response headers: " + e.responseHeaders) e.printStackTrace() } } } Code runs but this error is returned: Exception when calling SignatureRequestSendRequest Status code: 400 Reason: class ErrorResponse { error: class ErrorResponseError { errorMsg: Invalid email errorName: bad_request errorPath: null } } Response headers: {Server=[Apache], Access-Control-Allow-Origin=[*], Access-Control-Allow-Methods=[GET, POST, OPTIONS, PUT, DELETE], User-Agent=[HelloSign API], Connection=[keep-alive], P3P=[CP="NOP3PPOLICY"], Access-Control-Allow-Headers=[Authorization, Origin, X-Requested-With, Content-Type, Accept, Request-URL, Referrer-Policy, Referer, Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform, Sec-Fetch-Site, User-Agent, X-User-Agent], Date=[Tue, 12 Dec 2023 11:04:41 GMT], Strict-Transport-Security=[max-age=31536000], Vary=[Origin], Set-Cookie=[AWSALBCORS=Cl7ucvVmKGS9HdGnc+aly50OW37r7KwAYfYZAxMPfny5vzI0QrEV40pcbRrPkClxABELt5uFkurQEoSCI/3qqliESOtOn5BymbD0MI4bRhEujK0anS1QRSNb6A+6; Expires=Tue, 19 Dec 2023 11:04:41 GMT; Path=/; SameSite=None; Secure, AWSALB=Cl7ucvVmKGS9HdGnc+aly50OW37r7KwAYfYZAxMPfny5vzI0QrEV40pcbRrPkClxABELt5uFkurQEoSCI/3qqliESOtOn5BymbD0MI4bRhEujK0anS1QRSNb6A+6; Expires=Tue, 19 Dec 2023 11:04:41 GMT; Path=/], Content-Length=[66], Content-Type=[application/json]} com.dropbox.sign.ApiException: class ErrorResponse { error: class ErrorResponseError { errorMsg: Invalid email errorName: bad_request errorPath: null } } at com.dropbox.sign.ApiClient.invokeAPI(ApiClient.java:1095) at com.dropbox.sign.api.SignatureRequestApi.signatureRequestSendWithHttpInfo(SignatureRequestApi.java:1238) at com.dropbox.sign.api.SignatureRequestApi.signatureRequestSend(SignatureRequestApi.java:1181) at DropBoxSigner.sign(DropBoxSigner.kt:52) Can you please help me to understand which mail is invalid? The two provided in the example are place holders but i can guarantee that the one I've used are valid emails with no blank space around thanks1.4KViews0likes1CommentCan't resolve './aes' error when using @dropbox/sign
Node: 18.17.1 @dropbox/sign: 1.1.3 Hi, when I try to use the sdk I get the following error: - error ./node_modules/@dropbox/sign/dist/api.js Module not found: Can't resolve './aes' The error comes from this simple piece of code: import * as DropboxSign from '@dropbox/sign'; const signatureRequestApi = new DropboxSign.SignatureRequestApi(); Would be very greatful for any help on this. Best, S2.6KViews2likes10Commentscan other users use my app ?
im working on my app using the signature api and dropbox sign in. When i send out a signature request, the requester is always me, the one who owns the apis key. i want to make it so who ever is signed in to my app via the dropbox sign in is the requester https://api.hellosign.com/v3/signature_request/create_embedded this is the endpoint im using for the creating of the signature request.Solved1.5KViews0likes2CommentsGet Embedded Sign URL is asking for client id
when i run this code on my react app it gives me an error saying im missing the client ID parameters but in the documentation it dosent mention that , how am i suppose to make this call? Your request seems to have been malformed and returned the following error: → Missing parameter: client_id async function fetchSignUrl() { try { const response = await fetch(`https://api.hellosign.com/v3/embedded/sign_url/${signature_id}`, { method: 'GET', headers: { 'Authorization': `Basic ${btoa(API_KEY + ':')}` } }); if (!response.ok) { throw new Error(`HTTP error! Status: ${response.status}`); } const data = await response.json(); if (data && data.embedded && data.embedded.sign_url) { setSignUrl(data.embedded.sign_url); } } catch (error) { console.error("There was a problem fetching the sign URL:", error); } }Solved1.6KViews0likes2CommentsCreate Embedded Signature Request is not working with api key
im trying to use theCreate Embedded Signature Request api end point, but it is not working with my api key for the client_id parameter i tried using my secrete id and even myhellosign api key but i keep getting this error { "error": { "error_msg": "'client_id' must be 32 characters long", "error_path": "client_id", "error_name": "bad_request" } } i also have test_mode set to true and still get this error , any help is appreciated.712Views0likes1CommentDropbox sign refresh token getting expire after 1 hour
Hello, I have successfully implemented the authentication flow for the Dropbox Sign API and obtained the initial access token and refresh token. However, I noticed that the refresh token expires after only 1 hour, which requires frequent reauthorization and disrupts the seamless user experience. I expected the refresh token to have a longer validity period for smoother token management. authUrl='https://app.hellosign.com/oauth/authorize?response_type=code&client_id=12345678&redirect_uri=redirect-url&token_access_type=offline&state=121324234' ---------------------------------------------------------------- // code exchange req curl --location 'https://app.hellosign.com/oauth/token' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data '{ "code": "code", "grant_type": "authorization_code", "redirect_uri": "redirect_uri", "client_id": "client_id", "client_secret": "client_secret" }' Upon making a request for refresh token I am getting the below error req schema:- curl --location 'https://app.hellosign.com/oauth/token?=null' \ --header 'Content-Type: application/json' \ --data '{ "grant_type": "refresh_token", "refresh_token": "refresh_token" }' ______________________________________________________________________________ response:- { "error": "invalid_grant", "error_description": "Invalid grant data (refresh token)" } Thank you in advance for your support and contributions.1.6KViews0likes3Comments