Usage of the API is subject to an hourly rate limit and a daily call quota, whichever occurs first. The rate limits are based on a moving window that tracks the number of requests you make per hour.

The call quota is the maximum number of API calls that can be made in a 24 hour period resetting each day at midnight UTC.

Daily Call Quota Overview

The Foursquare API has a limit of 950 Regular API Calls per day and 50 Premium API Calls per day for Sandbox Tier Accounts.

By verifying your account using a credit card, you may upgrade your account to a Personal Tier Account to increase this limit to 99,500 Regular API Calls per day and 500 Premium API Calls per day. This can be done from the New Developer App page when creating your first app or the My Apps page if you have already created an app.

If you require more Regular or Premium Calls per day, please upgrade to the Start-Up Tier or contact us rather than create multiple Foursquare accounts.

The daily call quota resets each day at midnight UTC. If you are over the daily call quota limit, the Foursquare API will return a 429 error until the time of reset.

Hourly Rate Limit Overview

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

An application can make up to 500 userless requests to most other endpoints groups per hour.

An application can make up to 500 authenticated requests 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 the 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 and 2,500 userless requests to 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.