SilverStripe · Rate Limits
Silverstripe Rate Limits
SilverStripe does not enforce platform-level API rate limits out of the box. Rate limiting behavior depends on the specific REST or GraphQL module configuration and the hosting environment. Default ORM query limits apply to REST API responses.
Silverstripe Rate Limits is the machine-readable rate-limit profile for SilverStripe on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions.
Tagged areas include CMS, Content Management, GraphQL, REST API, and PHP.
3 Limits
CMSContent ManagementGraphQLREST APIPHPOpen SourceFrameworkPagesAssetsVersioning
Limits
GraphQL is an optional module in CMS 6. Developers are responsible for implementing their own rate limiting via server configuration (nginx, Apache) or application middleware.
The default result limit per REST API request is 30 records. The maximum configurable limit is 100 records, both of which can be adjusted in the endpoint configuration. No platform-enforced rate limits on request frequency exist by default.
Authentication uses an x-api-token header with the API Token value. The API_TOKEN_AUTHENTICATION permission must be granted to users consuming the API via token.