2025 sparked some incredible conversations across our community 👩💻. Discover the highlights and see what’s ahead in 2026.
Forum Discussion
scott_halgrim
4 years agoNew member | Level 2
/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
4 years agoI can't think of any reason you'd be seeing more calls to /2/files/search without actually calling filesSearch. For reference, here's a link to the code from v2.5.12 of the SDK, and the only reference to files/search is in the filesSearch definition. Could you perhaps share the relevant code you mention here: "the function from which I'm seeing the calls to the files/search endpoint do not call `filesSearch`" so we can take a look?
Also, filesSearch did not actually automatically handle the pagination for you. And there actually wasn't an equivalent /2/files/search/continue endpoint. The pagination for /2/files/search (and so for filesSearch) was handled by calling /2/files/search (filesSearch) itself again. With the SDK, when calling filesSearch you are supposed to check the returned FilesSearchResult.more to see if there are more results to retrieve, and then call filesSearch again, supplying the FilesSearchResult.start as FilesSearchArg.start, if so.
In the new version, using filesSearchV2 and filesSearchContinueV2, the pagination is built somewhat differently and uses the two separate endpoints, so you would instead check FilesSearchV2Result.has_more and use FilesSearchV2Result.cursor instead of a "start" value.
Finally, yes, the two search systems work a bit differently. You can find more information in this blog post.
shalgrim
4 years agoExplorer | Level 4
Thanks again, so much!
That's a great blog post, and I have a follow-up.
Is there a set of parameters I can send to search_v2 so that it will return the same results as search? I imagine we'll want to take advantage of the greater set of results, but just in case we run into cases it would be nice to have this in our back pocket.
Thanks!
- Greg-DB4 years ago
Dropbox Community Moderator
No, the two work a bit differently so their options and functionality don't map exactly to one another, so there isn't really a way to make them behave exactly the same way.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!