Plain · Rate Limits

Plain Support Rate Limits

Plain enforces rate limits on its GraphQL API at the workspace / API key level. Limits are applied per Machine User API key and are expressed as requests per unit time against the single POST /graphql/v1 endpoint; exceeding them returns an error (HTTP 429 / a RATE_LIMITED mutation error). Specific numeric thresholds are not published as fixed public values and are not reconciled in this artifact - confirm current limits with Plain.

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

It captures 3 rate-limit definitions, measuring requests, mutations, and deliveries.

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

Tagged areas include Customer Support, Help Desk, GraphQL, API First, and Rate Limiting.

3 Limits Throttle: 429
Customer SupportHelp DeskGraphQLAPI FirstRate LimitingQuotasThrottling

Limits

GraphQL Requests api_key
requests
see provider documentation
Per API key (Machine User) against POST /graphql/v1; varies by workspace and plan.
Mutation Operations api_key
mutations
see provider documentation
Write operations (upsertCustomer, createThread, replyToThread, etc.) are rate limited per key.
Webhook Deliveries workspace
deliveries
see provider documentation
Outbound webhook delivery attempts; failed deliveries are retried and inspectable.

Policies

Tiered / Workspace Limits
Limits are applied per API key and may vary by workspace and plan; contact Plain to raise them.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and RATE_LIMITED mutation errors.

Sources