Skip to main content

​
Limits

Rate limits are applied per user using a sliding window algorithm:
Auth MethodLimit
API Key10 requests/minute
Session20 requests/minute

​
Response headers

Every API response includes rate limit information in the headers:
HeaderDescription
X-RateLimit-LimitMaximum requests allowed per minute
X-RateLimit-RemainingRequests remaining in the current window
X-RateLimit-ResetUnix timestamp (seconds) when the limit resets
Example headers: 
X-RateLimit-Limit: 10
X-RateLimit-Remaining: 7
X-RateLimit-Reset: 1708100000

​
Exceeding the limit

When you exceed the rate limit, the API returns a 429 response: 
{
  "type": "https://api.rawugc.com/errors/rate_limit_exceeded",
  "title": "Rate Limit Exceeded",
  "status": 429,
  "detail": "Too many requests. Please retry after the rate limit window resets."
}

​
Best practices

  • Check headers before making additional requests to avoid hitting limits
  • Implement backoff when receiving 429 responses — wait until X-RateLimit-Reset
  • Batch operations where possible instead of making many individual requests
  • Cache responses for data that doesn’t change frequently (e.g., video status after completion)