We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Dropbox API call " /path/not_found " NEED HELP
I am attempting to make a API call from n8n that gets a files temporary link. My input data is directly from dropbox which is my correct file path. However the HTTP request keeps saying " /path/not_found " but when I use an already integrated action for drop the path file is correct and I can download, upload ETC. I need help finding why dropbox is consistently saying this error message.
Dropbox API Inquiry
I have to query the Dropbox Search API with a Team access token (i.e. scope team_data.member enabled). I learned that I have to include the 2 HTTP headers in the search API for my use case to work properly: Dropbox-API-Select-User: dbmid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Dropbox-API-Path-Root: {".tag": "namespace_id", "namespace_id": "XXXXXXXXXXXX"} That implies I have to call /users/get_current_account for every search API call unless I cache those values. Is there any way I can bypass putting these headers? Why can't Dropbox API extract the user ID via the access token instead? That's an OAuth2 standard. I have to enforce the file search in both user and team folders, hence specifying Dropbox-API-Path-Root. By answering the following questions, it will help me if I can hardcode this namespace_id for my use case: Is it possible for an organization/user to have multiple Dropbox teams? Is it possible for an organization to have multiple namespace_id? How is a namespace and team correlate to each other? When two different users in the same organization logged into Dropbox, is it possible they can have different root_namespace_id when they call /users/get_current_account?
SSL Certificate error or SSH md5 fingerprint not Ok error.
In our application we our using third party login to dropbox using OAuth. When the app is trying to load the login page it is showing error SSL Certificate error or SSH md5 fingerprint not Ok error while communicating with https://marketing.dropbox.com/oauth2/authorize and after that error shows with dropboxcaptcha.com. The login page is not able to load because of this error. Do anyone know why ? We have checked from our side regarding all the certificates in our application. The certificates are valid and have not expired. It looks like it is from the dropbox side.
LANGCHAIN DOC LOADER CANT ACCESS; SAYS MISSING SCOPE
I am using langchain_community.document_loaders.DropboxLoader the problem is with my api key. although in the permissions i have allowed files.metadata.read as well as write. but i get this error: AuthError('missing_scope', TokenScopeError(required_scope='files.metadata.read'))) anyone knows a thing about it?
Using API in Salesforce with Named and External Credentials and OAuth2 upload OK but call to file sh
I have setup OAuth2 in Salesforce along with Named Credentials and External Credentials. I am calling the File Upload API in the code..that works fine with all the above. I setup a second Named Credential that uses the shared External Credentials that the Upload API uses. The only real reason for this is the accomodate the different endpoints (why does Dropbox do this?). The Post to the Set Sharing /2/sharing/create_shared_link_with_settings endpoint uses the NamedCredential and gets a new/different bearer token. BUT, when that call is posted I get a 401 Unauthorized. The response says: {"error":{".tag":"missing_scope","required_scope":"sharing.write"},"error_summary":"missing_scope/"} The APP I defined in DROPBOX has sharing.write...so a little confuse. Where can I pass in that scope? Should I just generate a token in the APP for the one user...is that a permanent token that just replaces creds? UPDATE: I did use the APPTOKEN and that seems a better approach and calling OAuth each time. Its working, but now I have to figure out how to chunk load larger files. UGH Thoughts? Is there any reason getting a second token on a second HTTP callout is a problem when calling the different API?