Plausible · Rate Limits
Plausible Rate Limits
Plausible publishes a default Stats API rate limit of 600 requests per hour scoped to the API key, available on Business and Enterprise plans. The Events API (ingest) is open to all plans, returns 202 Accepted on success, and uses bot/IP heuristics rather than published per-key numerics. Higher Stats API capacity is available by contacting Plausible. The provider does not publish per-second numbers or rate-limit response headers in its public documentation.
3 Limits
Throttle: 429
Rate LimitingAnalyticsWeb AnalyticsPrivacy
Limits
Stats API default api-key
600
Default for Business plan; Enterprise plans can negotiate higher capacity by contacting Plausible.
Stats API enterprise api-key
negotiated; contact Plausible for higher capacity
No fixed published ceiling for Enterprise; raised on request.
Events API ingestion site
no published per-second / per-minute numeric; bot filtering and IP heuristics apply
All plans can post to /api/event. Server-side ingestion must set X-Forwarded-For to the real client IP or events will be dropped as bot traffic. Inspect x-plausible-dropped response header to detect filtering.
Policies
API Key Scoping
Stats API rate limits are evaluated per API key supplied via the Authorization Bearer header. Multiple keys per account are permitted.
Event Ingestion Filtering
The Events API silently accepts (HTTP 202) but may drop events that match bot heuristics. Use X-Debug-Request and check x-plausible-dropped to verify acceptance.
Capacity Increase
Higher Stats API throughput is available by emailing Plausible from the Business or Enterprise plan account.
Backoff
On 429 responses, clients should pause and retry with exponential backoff. The hourly window resets on a rolling basis.