Rybbit · Rate Limits

Rybbit Rate Limits

Rybbit applies API rate limits only on Rybbit Cloud and only to the Stats (read) API. Limits are per-plan: the Standard plan allows 20 requests per minute and the Pro plan allows 200 requests per minute (10x). Self-hosted instances have no rate limits. Exceeding a limit returns HTTP 429. The ingestion endpoint (POST /api/track) is governed by per-site ingestion controls rather than the published Stats API per-minute limits.

Rybbit Rate Limits is the machine-readable rate-limit profile for Rybbit on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and events.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Analytics, Web Analytics, Product Analytics, Privacy, and Open Source.

4 Limits Throttle: 429
AnalyticsWeb AnalyticsProduct AnalyticsPrivacyOpen SourceRate LimitingQuotasThrottling

Limits

Stats API - Standard Plan account
requests
20 per minute
Cloud Standard plan Stats API request rate.
Stats API - Pro Plan account
requests
200 per minute
Cloud Pro plan Stats API request rate (10x Standard).
Stats API - Self-Hosted instance
requests
unlimited
Self-hosted (AGPL-3.0) instances enforce no API rate limits.
Ingestion (/api/track) site
events
per-site ingestion controls
Tracking ingestion is rate-controlled per site, distinct from Stats API per-minute limits.

Policies

Plan-Tiered Limits
Cloud Stats API limits scale from Standard (20 rpm) to Pro (200 rpm); Enterprise is negotiated.
Self-Host Exemption
Open-source self-hosted deployments are not rate limited.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses.

Sources