Why Do We Limit API Access for Developers?
I am putting a lot of thought into why we limit API access for developers. I understand requiring keys to access APIs, and tracking who has access to your API, so you can understand how they are using it. What I don’t understand is why you’d want to limit API access.
By limit, I mean...here is an API, you get 100 calls, then no more! No option for paying, begging or pleading for more access. There are some APIs (I will evaluate specific APIs in the future), that have this approach, and it just doesn’t make sense to me.
Last year I touched on this subject with a post in ProgrammableWeb called, Should We Be Limiting Developers’ API Usage? Where I flip this model on its head and showcase two API providers, YellowAPI and ironically enough Qwerly (another story by itself), and how they were actually rewarding developers for more API usage.
I understand that in the early days, limiting access was a way to keep people from using their APIs too much, but I think in the era of cloud computing, that throttling as opposed to limiting is a better option. Let price control a developers API usage, and set that price at a level that is logical for this equation.
If your limiting developers from using your API, why even have one? It seems like you should sit down and re-evaluate your business model. I hope you don’t have other products that your customers can access, that at some point you cut them off and say, you can’t have anymore.