Comments
-
The /2/sharing/create_shared_link endpoint is deprecated in favor of the /2/sharing/create_shared_link_with_settings endpoint. Please switch to /2/sharing/create_shared_link_with_settings and let me know if you're still seeing a server error on that as well.
-
Can you clarify what you mean when you say "As far as I can tell the actual request from the deployed version is identical to the request sent by the local version"? Were you able to actually inspect the raw content of the request being sent from the deployed version? The output you shared here only shows some of the…
-
@"Здравко" To clarify, that is meant for the implementation in the official Dropbox SDK(s), and third parties can certainly use the official Dropbox SDKs, but third parties are not meant to re-implement the functionality using /1/connect themselves.
-
Please note that the /1/connect page is only meant for use by the official Dropbox SDK(s) and is not documented or intended for third party implementations. When implementing the OAuth app authorization yourself, please use /oauth2/authorize, documented here, e.g., as shown in my previous message.
-
@"Aadi12" It looks like you're using the Dropbox Java SDK to create some folders. When using createFolderBatch or createFolderBatchBuilder functionality, the resulting CreateFolderBatchLaunch may indicate either "launch an asynchronous job or complete synchronously". That being the case, you'll need to check which type it…
-
@"Thang2000" As Здравко said, the error you're getting is because of the extra "/" you have at the end of your "path" value. Remove that extra slash to get that to work. The Dropbox Java SDK offers the same search functionality. As for searching by tags only, unfortunately the Dropbox API (regardless of which SDK you're…
-
Regardless of where/how you're performing the API call, the "The given OAuth 2 access token is malformed" error should indicate that the call failed because the access token provided in the "Authorization" header was not of the expected form. This isn't something you need to or can configure for the app on the App Console.…
-
@"squidlauncher64" It is possible to use a custom URI scheme with the Dropbox OAuth app authorization flow, using the code flow with PKCE. For example, I just tried this out with an authorization URL like this:…
-
@"dmartinez" Здравко is correct; to access the contents of the team space, you'll need to set the Dropbox-API-Path-Root header, which you can do by using the with_path_root method in the Dropbox Python SDK. That way, you wouldn't need to use 'shared_link' at all. You can find more information on how to access team content…
-
@"rohitkmk" Здравко is correct; to access the team space you'd need to set the 'Dropbox-API-Path-Root' header. (It doesn't matter who owns/creates the app.) You can find more information in the Team Files Guide.
-
@"milankj" The /2/files/get_preview endpoint is still a valid way to get preview data for files of supported file types. Apps can use that returned data in their UI as needed. If you have any questions or issues regarding using the API, feel free to open a new thread with the relevant details.
-
Can clarify where you saw "com.dropbox.core.v2.webhooks.DropboxWebhookEvent" online"? That's not part of the official Dropbox API v2 Java SDK, for which you can find the official documentation here. In any case, using Dropbox webhooks actually does not require using any of the official Dropbox SDKs, and there are no…
-
That error indicates that you're using an access token/app that does not have the 'files.content.write' scope enabled. To resolve that, you'll need to enable that 'files.content.write' scope for that particular app, by using the "Permissions" tab of the app's page on the App Console, while signed in to the account that…
-
Can you clarify what you mean when you say "it is not working anymore"? For instance, what error or unexpected output do you get? For reference, regardless of what feature set your team is using exactly, if you're trying to access a "team space", you'd need to get the root namespace ID from users_get_current_account, and…
-
@"rohitkmk" I see Здравко already helpfully offered some guidance here, but if you're still having trouble with this, please feel free to share the relevant code/request that's failing with this error. Please be sure to redact any secret values, such as an app secret or access token though.
-
@"chainsbomb" As Здравко said, it's not necessary to use an SDK to access the Dropbox API, as you can construct the network requests directly. It is worth nothing though that the official Dropbox API v2 JavaScript SDK supports both back-end Node and front-end browser JavaScript environments. So, you can use a <script> tag…
-
With an /oauth2/authorize URL like that, the "Please sign in with a work account." message indicates that the app key in the client_id URL parameter is for an app that uses some team scope(s), but the account you're signing in to is not on a team. When using any team scopes, the app would be connected to the entire Dropbox…
-
@"query for dreambox" Regardless of the file type, substituting in 'dropboxusercontent.com' in Dropbox shared links like this is not something that Dropbox documents and may break without notice, and we can't offer technical support for issues that occur when doing so.
-
@"Igor6" The links returned by /2/files/get_temporary_link are only valid for four hours. Attempting to use one of these links more than four hours after the link was created will fail. You can find more information in the documentation for /2/files/get_temporary_link.
-
I can't offer help with Postman as it's not made by Dropbox. Please refer to the documentation for Postman for information on how to use it. If you're having any issues with the Dropbox API itself, please share the details of the issue so we can take a look.
-
@"dmartinez" Здравко is correct; for long-term access you should use a refresh token. Refresh tokens do not expire and can be used repeatedly. You do not need to re-authorize the app each time. Once you have a refresh token you can store and re-use that refresh token without further manual action. The official Dropbox…
-
@"query for dreambox" Unfortunately, using dropboxusercontent.com is not officially supported, so I can't offer help with that.
-
@"chakmangoo" To clarify, the /2/file_requests/list_v2 is for listing "file requests", not actual files. If you want to list the actual files in a folder, you should use /2/files/list_folder and /2/files/list_folder/continue. In any case, you shouldn't be receiving an "Empty reply from server" error; that may indicate an…
-
@"emretezisci" There isn't another endpoint for using a refresh token to get a new short-lived access token. If your platform doesn't natively provide support for writing the data as "application/x-www-form-urlencoded", I suggest checking your platform's documentation to see how you can supply a string instead so you can…
-
@"emretezisci" The /oauth2/token endpoint does not support those parameters being passed as "application/json"; they'll need to be passed as "application/x-www-form-urlencoded". While it is recommended to use some library or platform functionality to have that built automatically, as Здравко said you can otherwise try to…
-
Based on the error message, that looks like an issue interacting with the local filesystem, not the Dropbox API, so we can't offer help with that. I suggest referring to the documentation for your platform for information on how to access and debug use of the local filesystem.
-
You can use /2/files/list_folder[/continue] to list the files and folders under any particular path, but unfortunately the Dropbox API does not return the modification or creation date for folders in particular. I'll pass this along as a feature request, but I can't promise if or when that might be implemented. It does…
-
For information on how to use the authorization process, refer to the OAuth Guide and authorization documentation. If you use the official Dropbox API v2 .NET SDK from C#, you do not need to implement all of the code for this process yourself. The SDK will do most of the work for you. You can find examples of using this…
-
Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information on this migration here. Apps can still get long-term access by requesting "offline" access…
-
@"rafaelbelda" Здравко is correct; for long-term access you should use a refresh token. Refresh tokens do not expire and can be used repeatedly. You do not need to re-authorize the app each time. Once you have a refresh token you can store and re-use that refresh token without further manual action. The official Dropbox…