Greg-DB Dropbox Community Moderator

@"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…

I see Здравко already helpfully offered guidance on this, but for reference you can find more information about how this works on Dropbox at the following resources: * https://developers.dropbox.com/oauth-guide * https://www.dropbox.com/developers/documentation/http/documentation#authorization *…

Thanks for the feedback! I'll pass this along as a feature request, but I can't promise if or when that might be implemented.

New Dropbox access tokens are short-lived and expire after a short period of time, but refresh tokens do not expire and can be stored and re-used repeatedly. Once you have a refresh token for an account, you do not need to do the https://www.dropbox.com/oauth2/authorize... step for that account again; you can instead…

The Dropbox API can be used to upload to a shared folder in a connected account. For instance, an app can call /2/files/upload with a "path" parameter containing a path inside a shared folder. Note though that you'd need to use an app with the "full Dropbox" access type, not "app folder", to be able to access shared…

The team is reporting that this should be working again now. Please try again and let us know if you're still seeing any issues.

Thanks for the note! I'm raising this with the team to check on this.

For the API /2/files/move_batch/check_v2 issue, please share a sample async job ID so we can check on that. For the issue you showed on dropbox.com, please contact support to reach the relevant department. I can only help with use of the Dropbox API, not the web site.

I'm not sure I understand what you mean when you say "it give status in progress all the time". The /2/sharing/create_shared_link endpoint doesn't have a return type or error like that. Did you mean to refer to a different endpoint? Please do share a sample of whatever other issues you're seeing so we can be sure to check…

Please share a few samples for that (preferably as text). Thanks in advance! By the way, /2/sharing/create_shared_link is deprecated in favor of /2/sharing/create_shared_link_with_settings, so please switch to /2/sharing/create_shared_link_with_settings when you can.

I don't have an ETA on this right now, but I'll follow up here once I have any updates for you.

Thanks for the sample. I'll ask the team to check on that.

I can't provide help for the web site or support page, but if nothing seems to apply directly please feel free to use any option or contact method there and just explain in your message. The support agents can redirect the ticket as needed.

If you're still seeing issues, please share a few sample requests/responses showing the failures for each endpoint that's failing for you so we can check on that. Please include headers, but redact any app secret/access token/refresh token. Thanks!

It sounds like you may be seeing some lingering issues with your account after the earlier disruption. Since this happens both via the web site and API, please contact support so they can check on your account for you.

This dropins.js disruption should be fully resolved now. Please let us know if you're still seeing any issues with that. Thanks!

The team is reporting that this is related to that disruption, and is working to restore service.

Service is being restored so you should start seeing some success, but some issues may still linger while we get back to normal availability.

Thanks for the report! We're looking into that and I'll follow up here once I have confirmation or an update.