Posted on 03-03-2012
I am going through the Foursquare API, and found their section about how to get an increase in the number of calls you can make against the Foursquare API interesting:
If your application runs into any of our rate limits and you think you could use more, write us at firstname.lastname@example.org. We'llneed your OAuth consumer id, an explanation about why you need an increased cap, and information about the following
- Usage: A description of the endpoints you're calling and how you're using the data retrieved. We use this to make sure you're abiding by our Platform Policies and Terms of Service. Sample requests are generally helpful.
- Attribution: Screenshots of your application so we can confirm you're attributing foursquare correctly.
- Caching: Cache venue details where appropriate to avoid making spurious requests to our servers. See theRetention section of our Platform Policies for more details.
I like the idea of rewarding developers with the ability to make more calls against your API, when they adhere to your terms of service and benefit your operations.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma
- Exposing Dictionaries From My API Collections