CustomerOS · Rate Limits

Customeros Rate Limits

CustomerOS does not publish documented numeric rate limits for either the open-source customer-os-api GraphQL endpoint or the cloud Customerbase REST API. The self-hosted GraphQL server enforces no inherent quota beyond the operator's own infrastructure capacity. The cloud platform grants API access per endpoint group on a per-request basis and uses standard HTTP status conventions (2xx success, 4xx client error, 5xx server error). Specific RPM/RPD/concurrency values are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests.

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

Tagged areas include CRM, Revenue, Go-To-Market, GraphQL, and Open Source.

2 Limits Throttle: 429
CRMRevenueGo-To-MarketGraphQLOpen SourceRate LimitingQuotasThrottling

Limits

GraphQL Endpoint (self-hosted) deployment
requests
governed by operator infrastructure
The open-source customer-os-api /query endpoint imposes no documented quota; capacity is set by the self-hosted deployment.
Customerbase REST API (cloud) account
requests
see provider documentation
Cloud REST access is enabled per endpoint group on a per-request basis; numeric limits are not published.

Policies

Per-Request Access
Cloud API endpoint groups are enabled individually after contacting the CustomerOS team.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources