← Back to Documentation

Rate Limits

Understanding SEER API rate limits and best practices

Current Rate Limits
All SEER API endpoints share these limits
100
requests per minute
Applies to all plans • Shared across all API endpoints
What Counts Towards the Limit?
  • ✓ Job monitoring updates (success/error/progress)
  • ✓ Heartbeat pings
  • ✓ Pipeline status checks
  • ✓ Dashboard API calls
  • ✗ Dashboard page loads (not counted)
What Happens When You Hit the Limit?

If you exceed 100 requests per minute, you'll receive:

HTTP 429 Too Many Requests

Implement exponential backoff and retry logic to handle rate limiting gracefully.

Best Practices
  • Optimize heartbeat frequency: Send heartbeats every 5-15 minutes, not every second
  • Batch operations: Consolidate multiple small scripts into larger jobs
  • Implement retry logic: Use exponential backoff when receiving 429 responses
  • Cache dashboard data: Don't poll the API frequently for dashboard updates
Need Higher Limits?

If your use case requires higher rate limits, contact us at:

support@mg.ansrstudio.com