Foursquare has long partnered with the developer community, providing access to our API since 2009. In order for us to continue to serve more than 125,0000 developers and companies, we ask that you help us maintain our platform, and follow the rules listed below.
We understand that caching Foursquare may increase the speed of your application; however, we ask that you abide by the following rules around retaining Foursquare data:
- Checkins must be refreshed every 24 hours
- No piece of data can be kept for more than 30 days without being refreshed
- The data of users who haven’t authed your app may only be stored for up to three hours
For instance, if your app will display your users’ current location or contact information on a public page, they should know this before they authenticate and agree to use your app.
If your application uses our platform, you must attribute Foursquare as the source of your data through either general attribution (ie. buttons, our developer logo, etc.) or contextual attribution (ie. woven into copy, etc.).
Credit Card Validation
If you decide to verify your Foursquare Developer account, you will need to provide us with a major credit card, which we will only use to validate that it is a legitimate credit card. We use a third-party processor to validate your card. Foursquare does not view, process or store your credit card information.
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 send per hour. The default limit is 500 requests per hour per set of endpoints per authenticated user. We also allow 5,000 requests per hour to the venues/* endpoints when making userless requests.
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. By default, users can make 1,000 calls per day. This quota can be increased to 100,000 calls per day by verifying a credit card.