## Hourly Rate Limit Overview

An application can make a maximum of **5,000** userless requests per hour to venues/* endpoints.

An application can make a maximum of **500** userless requests to other endpoints groups per hour.

An application can make up to **500** authenticated requests per hour per OAuth token. For example, if your app has 3 connected users, it could make at most **500** requests on behalf of each connected user, for a maximum of **1,500** authenticated requests per hour.

Please note that rate limits are not per endpoint, but per top-level endpoint group. For example, in an hour, if you make **2,500** userless requests to [venues/search](https://docs.foursquare.com/developer/reference/v2-venues-search) and **2,500** userless requests to [venues/explore](https://docs.foursquare.com/developer/reference/v2-venues-explore), you would have exhausted your venues/_ rate limits for that hour; however, you would still have **500** requests left for tips/_.

Generally rate limits follow the rules above; however, some endpoints may have different limits due to security or other considerations. For the most current and accurate rate limit usage information for a particular request type, inspect the `X-RateLimit-Remaining` and `X-RateLimit-Limit` HTTP headers of API responses.

If you are currently over limits, our API will return a 403 error, and the response object returned by our API will be empty. We will also include a `X-RateLimit-Reset` header in the response, which is a timestamp that corresponds to when your rate limits will reset.

Updated 5 months ago