Pluralsight · Rate Limits
Pluralsight Rate Limits
Pluralsight gates its APIs behind Business, Enterprise, and Flow contracts. The provider does not publish per-key rate limits or rate-limit response headers in its public help center; abuse and concurrency thresholds are managed via the customer success team. Standard 429 responses apply on throttling. Consumers should implement exponential backoff and contact their account representative if they encounter sustained throttling.
3 Limits
Throttle: 429
Rate LimitingLearningEngineering Metrics
Limits
Skills GraphQL API (paas-api.pluralsight.com) api-key
not publicly documented; governed by fair-use
Subject to Business / Enterprise contract. Pagination is enforced (page-size caps in the GraphQL schema).
Flow REST API (flow-api.pluralsight.com / appfireflow.com) api-key
not publicly documented; governed by fair-use
Per-tenant. Bulk historical pulls should be paginated and run during off-peak.
Legacy Reports / Licensing REST APIs (app.pluralsight.com) api-key
not publicly documented; legacy endpoints scheduled for deprecation
Policies
Fair Use
Pluralsight does not publish numeric thresholds; sustained or abusive usage is handled by the customer success team rather than auto-throttle headers.
Backoff
On 429 / 503, retry with exponential backoff and jitter. Honor any Retry-After header if returned.
Pagination
GraphQL APIs require cursor-based pagination; do not request unbounded result sets.
Escalation
If you hit sustained throttling, contact your Pluralsight customer success manager to discuss higher capacity or batch export options.