# Using ETags Almost all of our endpoints will return an `ETag` in the HTTP Headers. `ETags` allow you to check if the data you have is up to date with what we are providing. Saving you the need of unnecessary requests. Requests you make using `ETags` do not count against your API rate limit. ### How To Use ETags When using an endpoint such as [Influencer Details](/core-resources/profile-details-twitter-id.md), there will be an `ETag` HTTP header in that response. Example: `ETag: 61eadf9f35830be5544441d03dd53a27` On subsequent requests to the same URL you can provide that ETag in your HTTP headers like so: `If-None-Match: ETAG_HERE` If your `ETag` is valid, your will receive a `304` status code. If it's not valid you will receive a `200` and the new data for that endpoint. To find out more about `Etags` click [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hive.one/using-etags.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.