This group is announcement-only. You cannot post messages because you are not a manager.
|
Changes coming to foursquare's "here now" feature
|
| |
Hey developers,
We’ll be updating ‘here now” in one month's time to better focus on foursquare’s goal of encouraging meaningful connections with new people and places.
When a user is checked in to a place, requests for "here now" data with that user's token will continue to return information about the other... more »
|
|
|
Announcing near= in api and geo/geocode
|
| |
*Hi api enthusiasts, I'm delighted to announce the integration of our coarse geocoder into the foursquare api today. The first integration is that venues and tips search & explore endpoints in the API which can take "ll" can now also take "near" instead. /venues/search?query=pizza&nea r=austin will return pizza places... more »
|
|
|
Changing domains for user photos
|
| |
Hey developers, We've changed the domain we serve user images from -- now instead img-s.foursquare.com, images will be hosted on domains like is1.4sqi.net. This change went into effect 3/13 and we'll be turning down img-s on 4/15 If you're refreshing data every 30 days, as per our platform policies<[link]>,... more »
|
|
|
New duplicate check-in merging logic
|
| |
Hey developers, We love all the apps that integrate with foursquare and allow users to push their content to foursquare as a check-in. Many of these integrations, however, didn't check if the user was already checked in to the venue and would overwrite a previous check-in made by the user (either via the... more »
|
|
|
venues/search finally accepts multiple categoryIds
|
| |
Hey devs, I'm happy to announce that the categoryId field of /venues/search now accepts a comma separated list of values for filtering results. I normally wouldn't bother to announce something so minor, but I know a lot of you have been eager for this change, so I wanted to make sure you all heard about it.... more »
|
|
|
New year, new endpoints
|
| |
Happy New Year everyone! We've pushed some new functionality recently and I wanted to keep you all up to date * For brand page users, we've renamed their type from "brand" to "page" in our endpoint responses, protected by version timestamp 20120104. - User objects now have a pageInfo section with content, when relevant... more »
|
|
|
Email verification woes? E-mail us for resolution
|
| |
Hey gang, I just talked to our community team and sounds like there's an ongoing issue with e-mail verification that's keeping a number of you from creating new consumer keys. If you're having this issue, please e-mail supp...@foursquare.com to have the issue resolved (it involves manual intervention on their part). You can... more »
|
|
|
Releasing limited "backdated check-in" functionality
|
| |
Hey kids, Due to a recent spike in demand, we're now making it possible to add historical check-in information for users via our API. The general idea is for developers to build tools helping users of other services bring their history into foursquare. It's a pretty big change around a sensitive part of a foursquare user's identity, so for now this... more »
|
|
|
