Start-Up Tier Launch
Date: April 12th, 2018
To developers who registered for the Foursquare Places API before April 12th:
Beginning on May 15th, we are making five changes in order to simplify our API and maintain the quality of our service as our developer community grows. Please find these changes below:
- The quantity of photos and tips per venue will be changed to 1 for Sandbox Tier and 2 Personal Tier
- Access to check-in counts, visit counts, chain details, and key tastes will be removed
- Venues search, explore, trending, similar, and next endpoints will return the following fields: venue name, venue ID, address, lat/long, and category. To access additional rich content for each venue, please call the details (venues/x) endpoint with venue ID as a parameter.
- Regular endpoints will have a quota of 950 calls per day for Sandbox Tier and 99,500 calls per day for Personal Tier. Premium endpoints will have a quota of 50 calls per day for Sandbox Tier and 500 calls per day for Personal Tier. More info on our endpoints can be found here.
- The caching time frame has been reduced to 24 hours. See here for more details.
To ensure that your applications continue to run smoothly, please make all necessary modifications to your integration prior to May 15th to prevent any disruption of service to your users.
TLS 1.2 Upgrade
Date: January 12, 2018
We recently announced that all Foursquare Places API developers will be required to upgrade to TLS 1.2 by March 1, 2018 to align with industry best practices for security and data integrity. If you’re using a modern HTTP framework or library, chances are you have no changes that need to be made. For older clients however, steps for upgrading to TLS 1.2 vary for different coding languages. Also, you can easily check your current TLS version by making a request to https://www.howsmyssl.com/a/check.
|8+||None, TLS 1.2 enabled by default|
|7||Explicitly enable TLS 1.2|
|6 and lower||TLS 1.2 not natively supported, upgrade to higher version|
Check your TLS version by running:
python -c "import json, urllib2; print json.load(urllib2.urlopen('https://www.howsmyssl.com/a/check'))['tls_version']"
python3 -c "import json, urllib.request; print(json.loads(urllib.request.urlopen('https://www.howsmyssl.com/a/check').read().decode('UTF-8'))['tls_version'])"
|3.3+||None, TLS 1.2 enabled by default|
|2.7.9+||None, TLS 1.2 enabled by default|
|2.7.8 and lower||TLS 1.2 not natively supported, upgrade to higher version|
Just verify your ruby environment is using
OpenSSL 1.0.2+ as TLS 1.2 will be enabled by default.
ruby -ropenssl -e 'puts OpenSSL::OPENSSL_VERSION'