Foursquare Places API (Self-Service)
End User License Agreement

Last Updated: February 29, 2024

If you have already entered into an enterprise agreement for access to one or more of our Products below, for so long as such agreement remains active, it will govern your use of the applicable Product(s) and, unless otherwise stated in such agreement, the terms below will not apply to you.

This Foursquare Places API (Self-Service) End User License Agreement (the “Places API EULA”) applies: (i)  to the self-service Foursquare Places API which Foursquare makes available on a pay-as-you-go basis to users via the Foursquare Developer Portal currently located at; and (ii) to the extent these terms are specifically referenced in your enterprise agreement with Foursquare. Capitalized Terms used but not defined in this Places API EULA have the meanings set forth in the Foursquare Developer Master Terms of Service (the “Master Terms”).

1 – License Grant

Subject to your full compliance with the Master Terms and this Places API EULA, during the Term, Foursquare grants you a limited, non-exclusive, revocable, non-sublicensable, non-transferable license, without rights to create any derivative works, to access and use the Places API to (a) develop, implement and integrate with application(s), website(s), product(s) and/or service(s) owned or controlled by you (“Your Service”); (b) call the Places API for Foursquare Places data (“Places Data”) using your Access Credentials; (c) use, reproduce, distribute, transmit, display and perform Places Data as part of Your Service; and (d) create external reports, analyses and demos (“External Materials”) using Places Data, so long as: (i) you provide Foursquare with branded attribution in connection with any External Materials, (ii) no material portions of the Places Data are exposed to third parties (as used herein, “material portions” means a set of data that could be marketed independently), and (iii) the External Materials are not competitive with Foursquare’s then-current products or services. You may not use the Places API for any other purpose without Foursquare’s prior written consent.

2 – Places API Requirements & Restrictions

In addition to the requirements and restrictions set forth in the Master Terms, you must also comply with the following in connection with your use of the Places API and Places Data:

2.1 – Caching & Rate Limits. You must comply with the Places API caching and query rate limitations applicable to your Account-type (Self-Service “Pay as You Go”) set forth in our Usage Guidelines in the Developer Documentation.

2.2 – Visual Crediting. You must provide Foursquare with branded attribution (i.e., ‘Powered by Foursquare’) on any page or screen within Your Service where Places Data may appear. You should review our Visual Crediting Policy to ensure that you are providing appropriate credit to Foursquare when displaying Places Data such that an end user would reasonably conclude that Foursquare is the source of such content.

2.3 – Display Rights Restrictions. You must make commercially reasonable efforts to prevent any pages or other properties displaying Places Data within Your Service from being crawled. A contractual prohibition (including legally binding terms of service or otherwise) preventing end users from crawling Your Service could be considered commercially reasonable and sufficient. Notwithstanding anything to the contrary, if certain attributes included in Places Data are not publicly available to users of the Foursquare City Guide mobile app or any successor thereto (e.g., “Calculated Scores” attributes and various other reliability metrics), then you may only use such attributes on an internal basis (and must not, for clarity, externally display such attributes or make such attributes available to users of Your Service or any third party).

2.4 – Navigation Services. If Your Service provides real-time route guidance, you must have an end user license agreement that includes the following notice: YOUR USE OF THIS APPLICATION IS AT YOUR SOLE RISK. LOCATION DATA MAY NOT BE ACCURATE.

2.5 – Other Restrictions. In addition, you shall not do any of the following:

2.5.1 – Provide access to the Places API or Places Data to third parties, except as integrated into Your Service as permitted by the licenses granted hereunder;

2.5.2 – Make Places Data available to third parties in bulk;

2.5.3 – Allow third parties to systematically query Places Data to obtain all or substantially all Places Data for a given locality, region, or country; or

2.5.4 – Use Places Data to contact businesses included in Places Data as prospective customers.

2.6 – Audit Rights. During the Term and for a period of six months thereafter, upon advance written notice, Foursquare may review your systems and applicable records as necessary to validate your use of Access Credentials, the Places API and all Places Data, during normal working hours, and without undue disruption to your operations. You acknowledge that Foursquare may disclose a copy of its findings to Foursquare’s data suppliers, upon their request, subject to standard confidentiality obligations.

3 – Additional Terms

3.1 – If Your Service uses Foursquare’s ‘autocomplete’ feature of the Places API (i.e., the ‘Address Data API’ and ‘Autocomplete API’ as described in the Developer Documentation), this Places API EULA incorporates these autocomplete terms.

3.2 – If you are an existing user of the prior version of the Places API (which includes any endpoints beginning with “/v2/”), then the following additional terms will apply to such use: (i) your access to the Foursquare Merchant API, if applicable, will remain subject to the “Additional Terms for ‘Merchant API’ Users” set forth in the Developer Documentation; and (ii) any calls you make to legacy “/v2/” endpoints will be subject to the applicable V2 pricing and rate limits set forth in the Developer Documentation.

3.3 – If you need to make authenticated calls using an OAuth access token, please reference the Developer Documentation. In addition, in connection with any authentication for users of Your Service, you agree that you will not directly or indirectly transfer any data resulting therefrom, including user data of Foursquare user IDs, to (or use such data in connection with) any ad network, ad exchange, data broker, or other advertising or monetization related toolset, even if a user consents to such transfer or use.

3.4 – If you configure your Places API implementation to transmit data to Foursquare that is subject to privacy or data protection laws, this Places API EULA incorporates our Global Data Processing Addendum.

3.5 – If you are a user of the geolocation software developer toolkit (currently known as Movement SDK), please reference our Movement SDK Developer Documentation.