API Endpoints

The Foursquare API provides methods for accessing a resource such as a venue, tip, or user. In spirit with the RESTful model, each resource is associated with a URL. For example, information about Clinton Street Baking Co can be found at

https://api.foursquare.com/v2/venues/40a55d80f964a52020f31ee3

(you need to supply your own credentials and version as extra parameters)

Given a resource, you can then drill into a particular aspect, for example

https://api.foursquare.com/v2/venues/40a55d80f964a52020f31ee3/tips

Each returned tip will have its own ID, which corresponds to its own resource URL, for example

https://api.foursquare.com/v2/tips/49f083e770c603bbe81f8eb4

Before diving into the endpoints below, it's generally useful to read our Getting Started Guide for an overview of high-level concepts and use cases.

GeneralAspectsActions
usersrequests
search
checkins
friends
lists
mayorships
photos
tastes
tips
venuehistory
venuelikes
approve
deny
setpings
unfriend
update
venuesadd
categories
explore
managed
search
suggestcompletion
timeseries
trending
events
herenow
hours
likes
links
listed
menu
nextvenues
photos
similar
stats
tips
claim
dislike
edit
flag
like
proposeedit
setrole
setsinglelocation
venuegroupsadd
delete
list
timeseriesaddvenue
edit
removevenue
update
checkinsadd
recent
resolve
likesaddcomment
addpost
deletecomment
like
tipsaddlikes
listed
saves
flag
like
unmark
listsaddfollowers
items
saves
suggestphoto
suggesttip
suggestvenues
additem
deleteitem
follow
moveitem
share
unfollow
update
updateitem
updatesnotificationsmarknotificationsread
photosadd
settingsallset
specialsadd
list
search
flag
eventscategories
search
add
pagesadd
managing
access
similar
timeseries
venues
follow
pageupdatesadd
list
delete
like
multi

Deprecated Endpoints

As we announced in our August Update, the endpoints below will be deprecated by the end of 2014.

GeneralAspectsActions
usersleaderboardbadges
todos
venuegroupscampaigns
tipssearch
specialsconfigurationretire
campaignsadd
list
timeseriesdelete
end
start