Slab · Rate Limits

Slab Rate Limits

Slab serves a single GraphQL endpoint (https://api.slab.com/v1/graphql) for Business and Enterprise customers. Slab does not publish specific numeric rate limits in its public developer documentation; large reads are expected to use cursor-based pagination rather than bulk export, and clients should handle HTTP 429 responses with backoff. Specific per-account limits are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests and results.

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

Tagged areas include Knowledge Base, Wiki, Documentation, Collaboration, and GraphQL.

2 Limits Throttle: 429
Knowledge BaseWikiDocumentationCollaborationGraphQLRate LimitingQuotasThrottling

Limits

GraphQL Requests account
requests
see provider documentation
No published numeric limit; throttling surfaces as HTTP 429.
Search / List Pagination account
results
cursor-based
Posts, topics, and users are returned via cursor-paginated connections (edges/pageInfo); there is no bulk export endpoint.

Policies

Cursor Pagination
Page through large result sets with first/after cursors and follow pageInfo.endCursor until hasNextPage is false.
Backoff Strategy
Implement exponential backoff with jitter on HTTP 429 and honor any Retry-After header.
Bot Access Scope
Responses are limited to content the Slab Bot user can access; add Slab Bot to private topics to make their content visible to the API.

Sources