Posted on 05-31-2012
In my effort to better understand API access, I’m studying how API owners control access to their APIs, with most recently being around Rate Limiting. The other day I asked, why do we limit API access for developers, and even explored rewarding developers for heavy usage.
As I continue to understand the impact of rate limits on developers it’s becoming clearer that for an API to successfully impose rate limits, you should also be offering rate limit release valves in the following ways:
- Increase Request Form - There should be a formal, self-service way to request rate limits either for valid uses that you hadn’t considered bumping up against rate limit ceiling, or quite possibly for non-commercial purposes.
- Utility Pricing - Providing a pay as you go model, where users meet the "courtesy limit", they can put in their credit card and pay for what they use above and beyond the default rate limit.
There are many points of friction for developers trying to integrate with an API. In my research, one of the ongoing complaints of developers regarding an API is around rate limits. Many of these complaints are directed at APIs who impose rate limits without any clear path beyond the default limits.
Google seems to be offering opportunities for developers to pay for use beyond their "courtesy limits", providing a form of release valve for developers concerns about API rate limits. Google is providing these release valves for API services via their API Console, but only appear to available for a handful of services.
While I’m still unsure about API rate limits in general, it seems clear that if you are going to limit, make sure and provide a release valve in some way, so developers understand what the options are when they hit the ceiling, and that there are opportunities to grow.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems