Papercups · Rate Limits

Papercups Rate Limits

Papercups does not publish formal, numeric API rate limits. Because it is open-source Elixir/Phoenix software that is typically self-hosted, effective throughput is bounded by the operator's own infrastructure, BEAM VM configuration, and any reverse-proxy throttling the operator places in front of the app. The hosted instance may apply its own limits, but these are not documented. Specific values are not reconciled in this artifact.

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

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

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

Tagged areas include Customer Messaging, Live Chat, Open Source, Support, and Intercom Alternative.

3 Limits Throttle: 429
Customer MessagingLive ChatOpen SourceSupportIntercom AlternativeRate LimitingQuotasThrottling

Limits

REST API Requests account
requests
not documented
No published numeric limit; bounded by self-hosted infrastructure or undocumented hosted limits.
WebSocket Connections (Phoenix Channels) account
connections
not documented
Bounded by BEAM VM and operator configuration; no published cap.
Webhook Delivery account
events
not documented
Outbound webhook delivery rate follows event volume; no published throttle.

Policies

Self-Hosted Control
Operators set their own limits via reverse proxy, load balancer, or Phoenix configuration.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After if a 429 is returned.

Sources