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 » By David Blackman  - Apr 5 2012 - 1 new of 1 message

	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 » By Akshay Patil  - Mar 21 2012 - 1 new of 1 message

	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 » By Akshay Patil  - Feb 16 2012 - 1 new of 1 message

	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 » By Akshay Patil  - Feb 6 2012 - 1 new of 1 message

	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 » By Akshay Patil  - Jan 20 2012 - 1 new of 1 message

	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 » By Akshay Patil  - Dec 15 2011 - 1 new of 1 message

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 » By Akshay Patil  - Dec 7 2011 - 1 new of 1 message

	Creators of Home Venues can now receive Venue Push API notifications
	For those of you who've wanted to play with our Venue Push API, but ran into the roadblock of creating/claiming a venue: good news! Last week we pushed a change and now apps that register for Venue Push notifications will receive check-ins from home venues created by their authenticated users (in addition to the usual managed venues).... more » By Akshay Patil  - Dec 5 2011 - 1 new of 1 message

	Updated foursquare attribution guidelines
	Devs! We've been pretty bad in the past about offering guidance about the attribution requirement in our Terms of Service. I know this has been a source of stress for some of you and it's been a long time to-do on my list to write clearer guidelines as to how to attribute foursquare when using our data in your application(s).... more » By Akshay Patil  - Dec 2 2011 - 1 new of 1 message