2025 sparked some incredible conversations across our community 👩💻. Discover the highlights and see what’s ahead in 2026.
Forum Discussion
/files/search deprecation and how it relates to the JavaScript SDK
Hey there, With regard to the deprecation of the /files/search endpoint, I'm curious how it relates to the JavaScript SDK. We're using an older verison of that SDK for our integration, and I'm wo...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThe /2/files/search endpoint is deprecated and is being retired in favor of the /2/files/search_v2 endpoint (and /2/files/search/continue_v2 for the pagination of results following /2/files/search_v2). Each of these endpoints correspond to one method in each official SDK. In the JavaScript SDK, that's:
- /2/files/search => filesSearch
- /2/files/search_v2 => filesSearchV2
- /2/files/search/continue_v2 => filesSearchContinueV2
Only filesSearch in the SDK calls the deprecated /2/files/search. In order to migrate from the deprecated endpoint to the new ones, you should replace any usage of filesSearch in your app with filesSearchV2 and filesSearchContinueV2.
Thanks so much for your help, Greg. I have some follow-ups.
We are currently on an old verison of the SDK. 2.5.12 to be exact, so we have some catching up to do.
My concern is still about the files/search endpoint that is about to be deprecated. We are seeing calls to that endpoint that are coming from places other than the filesSearch method. I don't know where they're coming from, but I can rule out they're coming from there. I have a hunch that it might be from filesListFolder or filesListFolderContinue.
So, is it the case that other functions in the SDK call filesSearch? What version of the SDK do I need to get to so that I can be sure that by eliminating all of our calls to filesSearch that files/search will never be hit?
(Context: If I jump all the way to 9.0.0 all of our tests fail. I've managed to so far get up to 5.1.0 and still have a working test suite, but even going from there to 6.x causes everything to fail.)
- Greg-DB
Can you elaborate on what you mean when you say you "are seeing calls to that endpoint that are coming from places other than the filesSearch method"? Can you share what you're seeing specifically in that regard? None of the other methods in the SDK should be calling that endpoint.
For instance, filesListFolder just calls /2/files/list_folder, and filesListFolderContinue just calls /2/files/list_folder/continue.
Also, for reference, you can find information about the changes between the versions in the release history and upgrading.md.
> Can you elaborate...
Right, well, in our logs I'm seeing calls to the files/search endpoint, but I can't trace how it gets there. We only call `filesSearch` in a single place; but the function from which I'm seeing the calls to the files/search endpoint do not call `filesSearch`. We're way back on version 2.5.12. This may not be a question you can answer, and that's fine, but it's very suspicious.
I do want to follow up on this bit, though:
> you should replace any usage of filesSearch in your app with filesSearchV2 and filesSearchContinueV2.
It seemed like `filesSearch` handled calling `files/search/` and `files/search/continue`. But now it seems like with moving to V2 we need to manage the continue call manually ourselves? In other words, we used to be able to call `filesSearch` and it did any continuing necessary under the hood but now we have to manage that ourselves?
Finally, one more question. I've noticed that the files/search and files/search_v2 endpoints return different results for the exact same query. Do you have documentation on what changes were made there?
Thanks!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
