Child Item

The results of "/files/search_v2" may be different.

Even though the request parameters are the same, the response results for "/files/search_v2" may differ. The response may contain search result folders/files, or it may contain zero search results.

Is it by design that the results can be different even though the request parameters are the same?
If it is a specification, I would like to know the reason why the results are different.

Thank you for your support.

Find more posts tagged with

API

Abuse

Comments

DB-Des

@ca-01,

The reason why there may be slight variations with the results from /files/search_v2 is not due to any specific specification, but rather how data is handled on the backend. Consistent results cannot be guaranteed because factors such as data updates, indexing, or backend processing that can impact the outcome of each search.

ca-01

@DB-Des

Thank you for your reply.

As of February 12, 2025, the number of search results was zero approximately one in three times, but as of February 17, 2025, the correct number of search results is returned even after 50 tries.

Have there been any fixes or improvements made on Dropbox's side?

DB-Des

@ca-01,

There have not been any recent changes made to the way searches are processed or results handled from the /files/search_v2 endpoint. Should this change in the future, we will make sure to publicly communicate this.

ca-01

Thank you for your reply.

Are there any mitigations or workarounds to avoid getting 0 search results ?
(For example, try again if the number of search results is 0, devise request parameters, etc.)

DB-Des

Hi @ca-01,

Since there isn’t an option to manipulate search results in the request, we recommend implementing logic in your integration to handle cases where 0 search results are returned.