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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/papercups-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.