Greg-DB Dropbox Community Moderator

Please clarify what you mean when you say "it doesn't work". For example, what unexpected error or output do you get from the API? From what you shared though, note that you need to implement filesListFolderContinue in addition to filesListFolder as documented to make sure you get all entries. You're not guaranteed to get…

To make sure I completely understand your post, can you share a sample request/response showing the call that isn't working the way you want? Be sure to redact your access token. If you'd prefer to share privately, you can open an API ticket here. Thanks!

@"athithan" To be clear, I can't promise if/when this would be updated accordingly, but I'll follow up here if I do get any news on this to share.

Thanks for the report. I'll ask the team to look into this.

Thanks for sharing this! I'll bring this up with the team to see if we can change that.

The sample you provided is working in Google Chrome on macOS for me. If something still isn't working for you, please share the exact steps to reproduce the issue, and the full error or unexpected output you're getting so we can look into it.

Currently, app folders are incompatible with shared/team folders, meaning you can't share an app folder, put a shared/team folder inside an app folder or put an app folder in a shared/team folder. (Though you can share app folders using shared links though, as you found.) Instead, if you need to use the API with…

@"gzowner" The issue we resolved earlier today wasn't specific to particular file types only, so you may be running in to something different. Can you share the steps to reproduce the issue, as well as a sample request/response that isn't working as expected for you so we can look into it? Be sure to redact your access…

I just tried this and it is working for me in Chrome. Are you still seeing an issue now? If so, please share a sample failing request/response so we can look into it. Thanks!

This should be fixed now. Please let us know if you're still seeing any issues.

This should be fixed now. Please let us know if you're still seeing any issues.

This should be fixed now. Please let us know if you're still seeing any issues.

This should be fixed now. Please let us know if you're still seeing any issues.

The fix is rolling out and is not out fully everywhere yet.

A fix is being rolled out. Please note it will take some to fully deploy it.

A fix is being rolled out. Please note it will take some to fully deploy it.

A fix is being rolled out. Please note it will take some to fully deploy it.

I'm not sure what you mean when you say you are "not getting any type of response from the curl command". For reference, if you need to debug something with curl, you can use the "-v" flag to enable verbose mode. In any case, I haven't tested your new code, but the parameters look right. I also don't see where you retrieve…

@"rylincoln" Thanks for the note. I wasn't able to reproduce that exact behavior, but depending on how your device/browser was trying to play the video, it may have been automatically sending 'Range'. In any case, I'm glad to hear you're seeing it working again. We have begun to roll out a fix. Please note it will take…

@"rylincoln" In my testing, this issue is not affecting requests not specifying "Range" to the temporary links returned by /2/files/get_temporary_link; I am not seeing the incorrect "Content-Type" in that case. Note that some media/video players do automatically set "Range" themselves though. If you are seeing otherwise…

@"ak2k" The team is actively working to resolve this issue as soon as possible.

@"needo" The team is currently working on resolving this issue. We'll follow up once we have an update on this.

@"b3nZol" Thanks for the feedback! I'll share this with the team.

You can find information on how to encode parameters on download calls here: https://www.dropbox.com/developers/reference/json-encoding If that doesn't help, please share the steps/code to reproduce the issue, including a sample parameter value that causes it to fail, and whatever unexpected error/output you get so we can…

@"Jeff B.63" As Здравко noted, your request is not formatted properly. You can find information on how to call the endpoint in the documentation. The API v2 Explorer can also be useful for prototyping these calls; you can click "Show Code" to see how the call would be constructed in a few different clients.

@"WoisWoi" I don't have an ETA on a fix to share right now. I'll follow up here once I have any news.

@"Andruy2003" I don't have a timeline to share right now. I'll post here when I have an update.

@"athithan" Thanks for the context! I've brought this up with the team and I'll follow up here with any news on this.

Access tokens and refresh tokens are different objects and are not interchangeable, so you can't use a refresh token as an access token like that. Instead, whenever you need a new short-lived access token you should call /oauth2/token with grant_type=refresh_token and refresh_token set to the refresh token, like in step 5…

@"jowflores" I don't have an update on this yet. I'll post here once I do.