Changes to API request rate

27 views
Skip to first unread message

Martin Butt

unread,
Jul 30, 2012, 5:43:56 PM7/30/12
to build...@googlegroups.com
Dear Kiva Developers,

We recently encountered some problems with users making excessive requests via the API. This put our server under a heavy load and had adverse effect to other Kiva users. For the sake fairness, we have decided to introduce a limit on the number of requests to our API. Initially we are setting this limit to 500 requests per minute, per IP address. This will affect a very small number of users. The change will go live on August 6th.

In the event that you exceed the limit, you will receive a 403 error and a temporary lockout. Your applications should account for the possiblity of a 403 and deal with it appropriately.

If you require access to Kiva's data in bulk, we have our snapshots available here: http://build.kiva.org/docs/data/snapshots. If you have a use case that is not met by the API or the snapshots, then get in touch! We are always excited to hear about how people are using our data in creative ways.

Regards,
    Martin

--

Martin Butt | Software Engineer

Kiva – Loans that Change Lives
Join us on Twitter
Facebook and LinkedIn!


Gary Mulder

unread,
Jul 31, 2012, 3:35:51 AM7/31/12
to build...@googlegroups.com
Hi guys,

I'm a software performance tester by trade. Do you need any help identifying what the performance issues with the API are?

Regards,
Gary

--
You received this message because you are subscribed to the Google Groups "build-kiva" group.
To post to this group, send email to build...@googlegroups.com.
To unsubscribe from this group, send email to build-kiva+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/build-kiva?hl=en.

Martin Butt

unread,
Jul 31, 2012, 11:08:14 AM7/31/12
to build...@googlegroups.com
Hi Gary,

Thanks for the offer. The problem was not in the API itself, but with the number of requests being made. They were being made in the range of a DoS attack.

Regards,
    Martin
Reply all
Reply to author
Forward
0 new messages