Skip to main content
To ensure high performance and stability, Sorsa API enforces a unified rate limit across all endpoints and plans.

📉 Unified Limit: 20 req/s

The limit is straightforward: 20 requests per second per API Key.
  • No complex windows: We don’t use 15-minute or hourly resets. As long as you stay within the 20 req/s threshold, you will never see a 429 error.
  • Universal: This limit applies to all endpoints (Search, Users, Tweets, etc.) and all subscription plans.
  • 1 Request = 1 Request: Whether you fetch a single tweet or a batch of users, it counts as one request against your total quota and the rate limit.

❌ Handling 429 Errors

If you send more than 20 requests in a single second, the API will return a 429 Too Many Requests error. How to stay safe: Since the limit is per second, you don’t need complex reset logic. Simply adding a small delay between your requests or using a semaphore/rate-limiter in your code is enough. Simple Python Example (Throttling): Python
import time
import requests

def fetch_data(urls, api_key):
    for url in urls:
        response = requests.get(url, headers={"ApiKey": api_key})
        
        if response.status_code == 429:
            print("Rate limit exceeded. Waiting 1 second...")
            time.sleep(1) # Wait for the next second window
            # Optional: retry the same request
            continue
            
        print(response.json())
        # To be safe, wait 0.05s (1/20) between calls
        time.sleep(0.05) 

❓ FAQ

Q: Do you have headers like x-ratelimit-remaining? A: No. Since the limit is a fixed per-second rate, tracking “remaining” credits in headers is unnecessary. Most users never hit this limit during normal operation. Q: Can I increase my limit? A: If your project requires massive scale (e.g., >100 req/s), please contact our support [email protected] to discuss a dedicated infrastructure setup.

⏭ Next Steps

  • Pagination — Learn how to efficiently fetch large amounts of data within the 20 req/s limit.
  • Error Codes — A guide to 400, 404, and 500 responses.