Considering an easier API limit strategy

API limitation can be a real annoyance for developers. You have to cache your requests and constantly make sure that your application does not exceed the access limit. Most notorious for this is Twitter and to make it easier for developers they've created a very nifty rate limit status API.

Now, as a lot of users on our message boards and mailing lists keep asking about the access limitations for our APIs and they do vary to a small degree we decided today to make the process much easier.

A new IP based access limit

Access to our services will be determined by your IP. On PCs simply go to the DOS console and type in "ipconfig" to find out your IP. On Macintosh computers go to the Terminal and type in "ifconfig". The result is something like the following (the relevant data is highlighted in green):

finding out your IP on a mac

To calculate your API access limit all you need is to follow this simple procedure:

Take the IP and remove all the dots, so becomes 1037129255.
Divide the result by 2009
Divide this result by 4
Divide this result by 1 (this is to make it round up nicely, some computers have bugs when you don't do this!)

This means that for the IP you get 89407 API requests a day - simple isn't it?

Access limit access distribution

You then define for each of your applications what percentage of the daily allowance it should use by using the new useAPILimitPercentageOfMyDailyAllowance parameter on your calls. For example for a use of BOSS you can say it should use 10 percent of your daily allowance:


Using the API limit calculator API

If the calculation of the API limit is too hard for you, you can also use the API Limit calculator. This one either gives you the information as a web page if you visit it:

The API limit calculator

Or you can use it as an API: gives you the data in XML. gives you the data in JSON. gives you the data in JSON and wraps it in a callback function.

We hope that this will make things much easier for all of us.

Have a wonderful day,

Chris Heilmann
Yahoo Developer Network