Usage Guidelines


Public Beta Feature

This documentation covers a feature currently in Public Beta. Access is available to anyone interested in building personalized experiences for their end-users.

This feature is subject to the Personalization API (Self-Service) Public Beta End user License Agreement 📄.

Foursquare has long partnered with the developer community, providing access to our APIs 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.

Please note: We reserve the right to terminate access to the Personalization API if you violate these rules or any of the terms listed in our Platform & Acceptable Use Policy, our Privacy Policies, or the agreement or subscription you have with Foursquare.

As used herein, an "Enterprise Customer" means only those customers with a duly executed agreement that expressly provides 'enterprise access' to the Places API is permitted. All other customers shall be subject to the 'Pay as You Go & Sandbox' terms below.

Data Retention

We understand that caching Foursquare data may increase the speed of your application. However, you must abide by the following rules around retaining data from the Personalization API:

  • venue_id: unlimited caching (solely to improve the performance of your application).
  • photo_id: unlimited caching
  • fsq_addr_id: unlimited caching

All Other Attributes:

  • Enterprise Customers: 24-hour local-device caching only (no server-based caching is permitted); or
  • Pay as You Go & Sandbox Customers: no caching permitted.

Your Privacy Policy

If your application accesses data shared by Foursquare users (e.g., user names, tips, or photos), you must publish a privacy policy that complies with applicable law (including any applicable privacy and data protection laws), including but not limited to how you source, use, and store user data.

If your application collects users’ location data (or any other sensitive data, as defined under applicable law), you must provide appropriate notice and collect appropriate consent from users, as required by applicable law.

Visual Crediting Policy

If your application uses our Personalization API, you must credit Foursquare as the source of your data through either visual credit (i.e., buttons, our developer logo, etc.) or contextual credit (i.e., woven into copy, etc.).

View Visual Crediting Policy
View Trademark Guidelines

Rate Limits

Usage of the Personalization API is subject to rate limits. Please refer to our Rate Limits for the Personalization API.