Help Scout

Help Scout MCP Server for Cloudflare Workers

Rate Limits & Quotas

Understand the rate limits and quotas for Help Scout API access.

Requests / Minute

57,600

Requests / Day

Burst Limit

Important Notes

•Help Scout API enforces a rate limit of 40 requests per minute per API key
•This translates to approximately 57,600 requests per day under normal conditions
•Burst limit is 40 requests per minute - exceeding this results in HTTP 429 (Too Many Requests) responses
•Rate limits are applied per API key, not per user account
•Help Scout recommends implementing exponential backoff for handling rate limit responses
•The API uses the X-RateLimit-* headers to communicate rate limit status to clients

Best Practices

Tips to avoid hitting rate limits

1.
Implement exponential backoff
When you receive a 429 error, wait before retrying with increasing delays.
2.
Cache responses when possible
Store frequently accessed data locally to reduce API calls.
3.
Use batch operations
Combine multiple operations into single requests where supported.
4.
Monitor your usage
Use the Primrose dashboard to track your API usage and set alerts.

Rate Limit Errors

What happens when you exceed limits

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Too many requests",
    "retry_after": 60
  }
}

When rate limited, the response includes a retry_after value indicating how many seconds to wait before retrying.