Foursquare API Rate Limit Increase Request
If you believe your application needs a rate limit increase, please fill out this form as accurately as possible. We'll consider your request in the order that it was received and will reach out to you soon after you submit.
Basic Information and Usage
Give us some basic info about your app so we can understand what you're building and make sure that you're abiding by our API policies, found at https://developer.foursquare.com/overview/community and https://foursquare.com/legal/api/platformpolicy.
What is your app's name?
Your answer
What is your app's client ID?
You can find the client ID for your app at https://foursquare.com/developers/apps
Your answer
Provide a brief summary of what your app does.
Your answer
What API endpoints does your app call and for what reason? About how many calls to each endpoint per user session? Please note any API calls that are not user-initiated (e.g., happen automatically upon app load)
For example, "venues/search to find restaurants nearby. About 3 times per session, all triggered by a user action," "checkins/CHECKIN_ID to determine what friends our users checked in with. Once automatically per session, more if they refresh"
Your answer
Provide us with some sample API calls you're making.
Optional
Your answer
If your app is already live in production, we want to play around! Give us instructions on how to download or test your app.
Your answer
Linking and Attribution
See https://developer.foursquare.com/overview/attribution for our policies on linking and attribution.

When providing screenshots, we recommend sharing links via Dropbox or CloudApp. If your app is still in development, it's fine to provide mocks or verbal proposals of how your apps will link and attribute Foursquare.

Share with us screenshots of where your app links to Foursquare venue pages.
If your app does not link, explain why you are not linking
Your answer
Share with us screenshots of how your app provides visual attribution to Foursquare.
Your answer
Caching
Utilize caching in your app to avoid making repetitive calls to the Foursquare API when different users request the the same information. Venue details (venues/VENUE_ID) don't change that often and caching this information can often dramatically reduce API volume. If you're calling venue details, we'll generally ask that you turn to caching first as a means to lower API traffic instead of asking for a rate limit increase.
What information does your app cache and how often do you refresh it?
Your answer
User Authentication
We strongly encourage developers to consider adding Foursquare authentication to their apps to automatically gain more favorable rate limits and to provide a better experience for your users. You're allotted 500 requests per hour per authenticated user, and API responses to search, venues, and other endpoints will be personalized to the user.
Does your application offer the ability for Foursquare users to log in?
Explain to us how logging in works or why you don't offer Foursquare auth.
Optional
Your answer
Additional Information
Congrats, you made it to the end! Just a few more things.
Is there anything else you want us to know about your application?
Optional
Your answer
What's your first name?
Your answer
What's your last name?
Your answer
What's the best email address to reach you to follow up with this request?
Your answer
Submit
Never submit passwords through Google Forms.
This form was created inside of Foursquare Labs. Report Abuse - Terms of Service - Additional Terms