API Rate Limit Fairness & Productivity Impact Survey

Welcome to this survey on your experience with API rate limits. This survey takes approximately 7–9 minutes. Your participation is voluntary and you may stop at any time. All responses are anonymous and will be reported only in aggregate. There are no right or wrong answers — we are interested in your honest opinions and experiences. By continuing, you agree to participate.

Which types of APIs have you integrated in the past 6 months? (Select all that apply.)

• Public REST/HTTP APIs
• GraphQL APIs
• gRPC services
• WebSocket/streaming APIs
• Cloud provider APIs
• Third-party SaaS APIs
• Internal microservice APIs
• SDK-only integrations
• Other

In the past 3 months, how often did you hit a rate limit on any API you use?

• Never
• Once
• 2–3 times
• About monthly
• About weekly
• Several times per week
• Daily or more

Overall, how fair were the rate limits you encountered in the past 3 months?

To what extent did rate limits slow down your development work in the past 3 months?

Please rank the following factors by how much they would improve your perception of rate-limit fairness (drag the most important to the top).

1. Clear documentation
2. Transparent tiers and upgrade paths
3. Predictable and consistent enforcement
4. Helpful error messages and headers
5. Representative sandbox limits
6. Flexible burst handling or grace periods
7. Responsive limit-increase process

Briefly describe a recent incident where rate limits affected your workflow or customers. What changed afterward?

Which role best describes your current position?

• Backend developer
• Full-stack developer
• Frontend developer
• Mobile developer
• Data/ML engineer
• SRE/DevOps
• Product manager
• Founder/CTO
• Other

Thank you for completing this survey! Your responses are anonymous and will be used in aggregate to help API providers improve rate-limit policies and developer experience.

Which rate-limit mechanisms have you encountered recently? (Select all that apply.)

• Fixed requests per minute/hour
• Burst plus sustained (token bucket)
• Leaky bucket
• Concurrency caps (simultaneous requests)
• Daily or monthly quotas
• Cost/compute unit budgets
• IP-based limits
• User or org-based limits
• Adaptive/dynamic throttling
• Not sure / Other

The rate-limit documentation I encountered was clear and easy to understand.

How severe was the most significant rate-limit incident you experienced in the past 3 months in terms of its downstream impact (e.g., on end users or business outcomes)?

What price increase would you consider acceptable for approximately 2× higher rate limits on a critical API?

• 0% — I wouldn't pay more
• 1–10%
• 11–25%
• 26–50%
• 51–75%
• 76–100%
• More than 100%

Based on your survey responses, is there anything else you'd like to share about your experience with API rate limits — what works well, what frustrates you, or what you wish providers would change?

How many years have you worked professionally with APIs?

• Less than 1
• 1–2
• 3–5
• 6–10
• 11 or more

When I hit a rate limit, the error messages and response headers gave me enough information to resolve the issue.

When you hit a rate limit, which actions do you typically take? (Select all that apply.)

• Exponential backoff/retry
• Queue or defer requests
• Batch or cache requests
• Optimize code to reduce API calls
• Request a higher tier or limit increase
• Switch to an alternative provider
• Use mirrors or proxies
• Throttle or limit end-user features
• Accept the limit / do nothing
• Other

What is your company size (total employees)?

• Just me
• 2–10
• 11–50
• 51–200
• 201–1,000
• 1,001–5,000
• 5,001+

Rate limits were enforced predictably and consistently across my requests.

Which region are you primarily based in?

• North America
• Europe
• Asia-Pacific
• Latin America
• Middle East
• Africa
• Other