# ?refresh or block on the Search API

**URL:** <https://discuss.elastic.co/t/refresh-or-block-on-the-search-api/289382>\
**Category:** Elasticsearch\
**Created:** [November 17, 2021, 1:41am UTC](https://discuss.elastic.co/t/refresh-or-block-on-the-search-api/289382 "2021-11-17T01:41:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryji](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bryji/32/97188_2.png) [@Bryji](https://discuss.elastic.co/u/Bryji)\
**Post date:** [November 17, 2021, 1:41am UTC](https://discuss.elastic.co/t/refresh-or-block-on-the-search-api/289382/1 "2021-11-17T01:41:22Z")

</div>

It would be nice if the Search API supported [?refresh](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-refresh.html) like the Index/Update/Delete APIs, so that requests could block until a consistent result could be returned. Has this ever been discussed / proposed? Any other suggestions on how this might be implemented? I guess in theory you could "wait one second" and the `near-realtime search` would be in play, but looking for something more deterministic.

Also wondering what the boundary scenarios for the "1 second" refresh are - how dependent on the current load on the cluster e.g.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 15, 2021, 1:41am UTC](https://discuss.elastic.co/t/refresh-or-block-on-the-search-api/289382/2 "2021-12-15T01:41:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.