Rate Limits & Quotas

ℹ️ Overview

Wp Admin implements rate limiting to ensure platform stability, fair usage across all clients, and protection against abuse. Limits are applied per API key and vary based on your subscription tier. When a limit is reached, requests will receive a 429 Too Many Requests response until the window resets.

💡

Most standard WordPress management workflows fall well within the Starter tier limits. Contact us if you're running high-volume automation or agency-scale deployments.

📊 Limits by Plan

Metric	Starter	Professional	Enterprise	Notes
API Requests (per minute)	60	300	1,000	Sliding window algorithm
Concurrent Connections	5	25	100	WebSocket & REST combined
Webhook Deliveries (per hour)	500	5,000	50,000	Retries included in count
Daily API Calls	10,000	100,000	Unlimited	Resets at 00:00 UTC
Batch Operations	10 items/request	50 items/request	200 items/request	Max payload: 5MB

🔐 Response Headers & Status Codes

Every API response includes rate limit headers to help you monitor your usage in real-time. Always check these headers before making subsequent requests.

# Rate Limit Headers
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 287
X-RateLimit-Reset: 1718456400

# When limit is reached
HTTP/1.1 429 Too Many Requests
Retry-After: 42 # Seconds until reset

# Sample JSON body
{
  "error": "rate_limit_exceeded",
  "message": "You've exceeded your API rate limit. Please retry after 42 seconds.",
  "retry_after": 42
}
            

⚠️

Never ignore the 429 status or Retry-After header. Continuous requests after a limit breach may result in temporary API key suspension.

✅ Best Practices

Follow these guidelines to maximize efficiency and avoid hitting rate limits unexpectedly.

🔄 Exponential Backoff

Implement retry logic with exponential backoff and jitter. Wait 1s, then 2s, 4s, 8s... up to 60s, adding random variance to prevent thundering herds.

📦 Use Webhooks

Replace polling with webhooks for real-time events. Webhooks have separate limits and significantly reduce unnecessary API calls.

⚡ Cache Responses

Cache static or rarely-changing data (site info, plugin lists) locally. Set appropriate TTLs based on your update frequency needs.

📜 Paginate & Batch

Always use pagination for list endpoints. Group related operations into batch requests when supported to minimize round trips.

Need Higher Limits?

Running a high-traffic site or agency workflow? Our Enterprise plan supports custom rate limits tailored to your infrastructure.

Request Limit Increase →