API Docs
  • Welcome
  • Key Concepts
  • Authentication
  • Response Codes
  • Using ETags
  • Core Resources
    • List of Available Influencers
    • Top Influencers
    • Influencer Details (Twitter ID)
    • Influencer Details (Twitter Screen Name)
    • Influencer Rank/Score History (Twitter ID)
    • Influencer Rank/Score History (Twitter Screen Name)
    • Influencer Podcasts (Twitter ID)
    • Influencer Podcasts (Twitter Screen Name)
    • Batch Influencers Details (Twitter ID)
Powered by GitBook
On this page

Was this helpful?

Using ETags

PreviousResponse CodesNextList of Available Influencers

Last updated 5 years ago

Was this helpful?

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 , 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

Influencer Details
here