# Refresh API and Search API **URL:** \ **Category:** Elasticsearch\ **Created:** [February 5, 2015, 10:51pm UTC](https://discuss.elastic.co/t/refresh-api-and-search-api/22003 "2015-02-05T22:51:43Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Chris\_Robison](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_robison/32/929_2.png) [@Chris\_Robison](https://discuss.elastic.co/u/Chris_Robison)\ **Post date:** [February 5, 2015, 10:51pm UTC](https://discuss.elastic.co/t/refresh-api-and-search-api/22003/1 "2015-02-05T22:51:43Z")
I know there have been a lot of posts about the refresh api and trying to achieve real time searching. We have a situation where we update a bunch documents and then we call refresh in an attempt to make them immediately available to the search API (not the get API), but we have found that, that is not the case. Does the refresh API call block until it is done refreshing? We normally let ElasticSearch run refresh on its own, but there are a few instances where we need changes immediately. Any suggestion? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/12ab9e32-7345-4022-adbc-a1bd10d122a6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/12ab9e32-7345-4022-adbc-a1bd10d122a6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Chris\_Robison](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_robison/32/929_2.png) [@Chris\_Robison](https://discuss.elastic.co/u/Chris_Robison)\ **Post date:** [February 6, 2015, 12:01am UTC](https://discuss.elastic.co/t/refresh-api-and-search-api/22003/2 "2015-02-06T00:01:52Z")
After banging our heads we realized it was our problem and not ES. On Thursday, February 5, 2015 at 3:51:44 PM UTC-7, Chris Robison wrote: > I know there have been a lot of posts about the refresh api and trying to > achieve real time searching. We have a situation where we update a bunch > documents and then we call refresh in an attempt to make them immediately > available to the search API (not the get API), but we have found that, that > is not the case. Does the refresh API call block until it is done > refreshing? We normally let Elasticsearch run refresh on its own, but there > are a few instances where we need changes immediately. Any suggestion? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/fe262a59-1a33-43a1-95d8-58284fe5beba%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fe262a59-1a33-43a1-95d8-58284fe5beba%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:34am UTC](https://discuss.elastic.co/t/refresh-api-and-search-api/22003/3 "2017-07-06T00:34:38Z")