We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
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);
API Upload .HEIC and convert to JPG
I am using the API to upload images and make them public. I get the public link back and embed in my application. ALL GOOD. Now I am looking to allow .HEIC uploads. I don't see anything in the API to cause the conversion. So, I put automation on my parent folder and that seems to create another duplicate photo converted to JPG. At that point I assume I have lost the public link and I have duplicate files. I am looking for any pointers here..... thanks in advance.
Invalid Folder Name with Team API
I am trying to create folders using the api in a team folder like this: // Get Namespace ID const dbx = new Dropbox({ accessToken: process.env.DROPBOX_ACCESS_TOKEN }); const baseFolder = "/Data Transfers"; const customerFolder = `${baseFolder}/${folder_name}`; const dataFolder = `${customerFolder}/data`; // Create a folder in dropbox await step.run('create-customer-folder', async () => { console.log(customerFolder); await dbx.teamTeamFolderCreate({ name: customerFolder }); await dbx.filesCreateFolderV2({ path: dataFolder }); }); This should be just to create a folder under our team/Data Transfers/TestFolder but it is giving me an Invalid Folder name, what am I doing wrong? I am just getting started with the API and I am completely lost.
Know uploaded by user of a file and folder
Hi, I am developing an application where I need to know the user who uploaded particular file. I checked that dropbox UI has that information available and it fetches it from https://www.dropbox.com/2/files/get_upload_infoendpoint. This endpoint is not listed in dropbox API documentation. Also, response returned by it only contains displayName and uploadTime of the file which is not sufficient to uniquely identify the user. Is there any better API available to know uploaded by user of a file and folder?
I can no longer upload files
Hi all, For some time now I have not been able to upload my files via the HTTP API. The file/upload or file/get_temporary_upload_link gives me a 404 error even though it worked perfectly until now. If I do CURL tests then everything works perfectly, so I suspect an unsupported header. Here is the list of headers on my HTTP request (I use python/requests to do this): Headers: {'User-Agent': 'python-requests/2.25.1', 'Accept-Encoding': 'gzip, deflate', 'Accept': '*/*', 'Connection': 'keep-alive', 'Content-Type': 'application/octet-stream', 'Dropbox-API-Arg': '{"mode":"overwrite","path":"/Sans nom 1.odt","autorename":false,"mute":false,"strict_conflict":false}', 'Content-Length': '473722', 'Authorization': 'Bearer sl.B_3Hk1dv...'} I'll try adding these headers to CURL to see if that's where it comes from, but I'm interested in any good information. Thanks.