Posted on 05-29-2012
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.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Why I Am Continuing To Integrate Zapier In My Business Workflow
- Who Is Going To Build The Uber API Platform For The Sharing Economy?
- The API Focused Dev Shop
- Route SMS Messages To Google Spreadsheets Via Twilio API With TwilioSheet
- Publishing Your APIs To Product Hunt
- Providing Users With Reciprocity Tools So Important Intuit Purchases itDuzzit
- Bing Developer Assistant for Visual Studio Delivers Relevant API Code
- Average Number of APIs Used In A Modern App
- An APIs.json Collection Of API Resources Across Your Public, Partner Or Internal Resources
- One Possible Reboot Of The API Stack
- How Are Dev Shops In Chicago Using APIs? A Talk With Bryson Pouw At Blaze Portfolio
- Every API Provider Should Have A Logo And Branding Page
- What Is An API First Strategy? IT architecture And Catalyst For Engagement
- The Speed Of Federal Government When It Runs On Github
- Swagger, APIs.json, And Review For The New Developer.Trade.gov
- Student, Instructor, Classroom, Class, And Course API Planning At BYU
- Can You Add My API To Your Website Listing?
- Adding Google To List Of API Deployment Companies
- What Is An API First Strategy? Adding Some Dimensions To This New Question
- The Five Month Journey Toward A Stable APIs.json Discovery Format
- How Are Mobile Dev Shops In Chicago Using APIs? A Talk With Dave Devitt At SYDCON
- An API Case Study Format From Google Cloud Platform
- Next Stable Version of APIs.json + APIs.io Is Ready - Are Your APIs Discoverable?
- Expanding API Gateway Connectors Into A World of API Deployment Startups
- Where The Good IPAs Are In Chicago While At API Strategy And Practice In September