# How does the GET API function internally in real time?

**URL:** <https://discuss.elastic.co/t/how-does-the-get-api-function-internally-in-real-time/315734>\
**Category:** Elasticsearch\
**Created:** [October 4, 2022, 5:54am UTC](https://discuss.elastic.co/t/how-does-the-get-api-function-internally-in-real-time/315734 "2022-10-04T05:54:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhavya](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavya/32/45679_2.png) [@bhavya](https://discuss.elastic.co/u/bhavya)\
**Post date:** [October 4, 2022, 5:54am UTC](https://discuss.elastic.co/t/how-does-the-get-api-function-internally-in-real-time/315734/1 "2022-10-04T05:54:46Z")

</div>

Under the hood of the most recent operation, Elasticsearch records the value of the \_version meta field, primary term, and sequence number. We may use the GET API to obtain these meta field values and add them to the search query parameter to resolve the conflicts.

I've read that the GET API operates in real-time, but I'm curious how Elasticsearch internally implements this ?

---

<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:** [November 1, 2022, 5:55am UTC](https://discuss.elastic.co/t/how-does-the-get-api-function-internally-in-real-time/315734/2 "2022-11-01T05:55:21Z")

</div>

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