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.
Filter by
All · Core API · Venues Platform · Merchant PlatformAs we announced in our August Update, the endpoints below will be deprecated by the end of 2014.
| General | Aspects | Actions | |
|---|---|---|---|
| users | leaderboard | todos | |
| venuegroups | campaigns | ||
| tips | search | ||
| specials | configuration | retire | |
| campaigns | list add | timeseries | end delete start |