rate limits howto

[naveen]

I've posted about this once before, but just went back to the docs to
more thoroughly clarify how this works (because we're getting a lot of
email back-and-forth we'd like to avoid – anything to make less work
for us :)

Usage of the API is subject to rate limits. The limits are based on a
moving window that tracks the number of requests you send per hour.

The default limit is 200 requests per hour per method. The rate
limiting is applied to one of the following, in this order:
- the basic auth login
- OAuth consumer key
- IP address

Your application should try to play nicely against our methods. For
instance, cache results on your side wherever possible (e.g., /venue
calls usually tend to be more long-lived than others). Send back an
identifiable User-Agent header.

We're still learning about your apps and tweaking these caps. If your
application runs into any of our bounds and you think you could use
more, write us: api@foursquare. Depending on the method you are using
to access our API, we'll need one of the following:
- Basic authentication: your user name
- OAuth: the email address you used to register with foursquare _and_
your OAuth consumer key
- Anonymous: IP address of the machine from which you are making
calls

naveen

[Steven Bourke]

Any chance of taking the load off foursquare and developers by providing some additional methods such as a larger search radius for venues? I just want to get hold of venue id's in my postal area, that requires a large number of requests. This kinda data is almost static.

--
To post to this group, send email to foursqu...@googlegroups.com

http://groups.google.com/group/foursquare-api

[naveen]

On Wed, Jul 7, 2010 at 6:41 PM, Steven Bourke <sbo...@gmail.com> wrote:

Any chance of taking the load off foursquare and developers by providing some additional methods such as a larger search radius for venues? I just want to get hold of venue id's in my postal area, that requires a large number of requests. This kinda data is almost static.

yes, currently thinking on all this

more on this shortly in v2

[Kenneth]

Hello! For the rate limit of 200 requests per hour per method, is it
on a per user basis? For example, if each user logs in with their
foursquare credentials and we use basic authentication, does the 200
request only apply to that user? Right now we use basic authentication
for Foursquare check in and tips, but for pulling in nearby venue
locations we don't authenticate. Does the rate limit apply for that
request?

Thanks so much! Loving the API. Keep up the great work!!! Can't wait
to see what's in store with v2!

On Jul 7, 4:29 pm, naveen <naveen...@gmail.com> wrote:

[Ryan Williams]

Yes, the 200 limit definitely applies to the venue search call, so it
would probably be a good idea to use the basic auth or oauth for that
call too if you have it. If 200 users do a search, with no auth,
you're at the limit right then. If you're on shared infrastructure
(i.e. App Engine), you'll hit the limit even faster. Authenticate
wherever possible to stay under the limit.