We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
API
5741 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);35Views0likes0CommentsAPI 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.463Views0likes7CommentsInvalid 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.89Views0likes1CommentZapier - 409 error path/not found
Hello everyone! I'm trying to get the meta data for a file so I can access the "shared_folder_id" and then add a member (or group if possible) to that folder. It's on a team folder. I'm using Zapier as I want this to be automated upon a trigger. The issue I get is during a Post request to get_metadata, the path cannot be found (error 409) I first find a folder, which returns correctly. Then I run a custom request (http) for: https://api.dropboxapi.com/2/files/get_metadata Data: { "include_deleted": false, "include_has_explicit_shared_members": false, "include_media_info": false, "path": "<path from the previous find folder path in zap>" } I've also verified this folder path does exist (I can see it, and it's all spelt correctly). This leads me to believe it's a access or permission error, but I'm not confident. Headers: AuthorizationBearer <my actual token id> Content-Typeapplication/json Dropbox-API-Select-Admin.dbmid:<my actual token id for myself as an admin user> The folder I'm accessing has myself listed as access, and I'm also included in a group that has access. I've selected all permissions on my app to write/edit everything, generated a new auth token after saving, and I still have issues. Any help is much appreciated. I'm happy to provide any additional information as well. Thanks in advance!Solved1.7KViews0likes12CommentsKnow 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?449Views1like6CommentsUnable to share folders since migration to updated team space
Back in June, our Dropbox Business account was migrated to the Updated Team Space system. We have a custom application that manages automatically uploading files and sharing folders with our customers. Everything was working fine prior to June, new files could be uploaded, folders could be shared, and folder members could be added. After the account was migrated, all of the functionality broke, as expected. We were able to fix file uploads by grabbing the new root_namespace_id for the account, but we have not been able to share folders since the account migration. This is the response from the `get_features` endpoint for our account, which I believe indicates we are on the updated team space: { "values": [ { ".tag": "has_team_shared_dropbox", "has_team_shared_dropbox": { ".tag": "has_team_shared_dropbox", "has_team_shared_dropbox": false } }, { ".tag": "has_distinct_member_homes", "has_distinct_member_homes": { ".tag": "has_distinct_member_homes", "has_distinct_member_homes": true } } ] } Here are the scopes granted to our application: files.metadata.write files.metadata.read files.content.write files.content.read sharing.write sharing.read file_requests.write file_requests.read contacts.write contacts.read Here's an example of a file upload call that succeeds: fetch('https://content.dropboxapi.com/2/files/upload', { method: 'POST', headers: { 'Content-Type': 'application/octet-stream', 'Dropbox-API-Arg': JSON.stringify({ path: `/Client Files/${customer.name}/${file.name}`, mute: false, }), Authorization: `Bearer ${token}`, 'Dropbox-API-Select-Admin': adminId, 'Dropbox-API-Path-Root': JSON.stringify({ '.tag': 'namespace_id', namespace_id: rootNamespaceId, }), }, body: buffer, } However, after updating the share_folder call, we are getting {".tag": "no_permission"} responses. Here's how we are attempting to share new folders created by the app: fetch('https://api.dropboxapi.com/2/sharing/share_folder', { method: 'POST', headers: { Authorization: `Bearer ${token}`, 'Content-Type': 'application/json', 'Dropbox-API-Select-Admin': adminId, 'Dropbox-API-Path-Root': JSON.stringify({ '.tag': 'namespace_id', namespace_id: rootNamespaceId }), }, body: JSON.stringify({ path: `/Client Files/${customer.name}`, member_policy: 'anyone', }), }); We've gone a few rounds trying different permutations of Dropbox-API-Select-Admin, Dropbox-API-Select-User, and Dropbox-API-Path-Root options, but we have had no luck. I don't know if this matters, but here's the metadata for the "/Client Files" folder: { ".tag": "folder", "name": "Client Files", "path_lower": "/client files", "path_display": "/Client Files", "parent_shared_folder_id": "<root namespace id>", "id": "id:<id>", "shared_folder_id": "<number>", "sharing_info": { "read_only": false, "parent_shared_folder_id": "<root namespace id>", "shared_folder_id": "<number>", "traverse_only": false, "no_access": false } }Solved292Views0likes2CommentsImages for gallery
I am a novice, sorry for the lame question, but I need to make an app that searches images based on their tags. Since all apps are located in the Applications/[my app] folder, all images to be sorted (3K+) need to be relocated into this new folder? If so, is there a way to make a redirecting link to the existent folder I already have?Solved1.1KViews0likes2CommentsI 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.314Views0likes5CommentsDropbox Error 401: Unauthorized API Call
Hello, guys. I'm having unexpected issues trying to download all the files in a folder from Dropbox using the "https://content.dropboxapi.com/2/files/download_zip" API Call Request. But, I keep receiving the 401 unauthorized error message when I have already given the permissions: files.content.write files.content.read sharing.write sharing.read Then I've created a new token and placed the request as explained in many forums and API docs from Dropbox but I keep receiving the same error. I need it to be used through make Integromat so I'm doing my tests through Postman and the error is the same thing. I'm using these parameters: {"path": "/Automatización Inteligente/CSV/"} and the Access TokenSolved436Views0likes8Comments