Leapsome · Rate Limits
Leapsome Rate Limits
Leapsome publishes limited rate limit documentation. The SCIM API enforces a maximum of 30 parallel requests per second, returning HTTP 429 when exceeded. The Content API does not have publicly documented rate limits; developers should implement exponential back-off when receiving 429 responses and contact Leapsome support to discuss enterprise throughput thresholds.
Leapsome Rate Limits is the machine-readable rate-limit profile for Leapsome on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions.
Tagged areas include People Enablement, Performance Management, OKRs, Goals, and Engagement Surveys.
2 Limits
People EnablementPerformance ManagementOKRsGoalsEngagement SurveysHRISSCIMEmployee Development1:1 MeetingsLearning
Limits
Parallel requests
30
The SCIM API restricts parallel (concurrent) requests to 30 per second. Clients exceeding this limit receive a 429 Too Many Requests response. Retry-After header behavior is not publicly documented; implement exponential back-off in client code.
General requests
Not publicly documented
No public rate limit documentation exists for the Content API. Leapsome recommends implementing exponential back-off on 429 responses. Enterprise customers should contact support for specific throughput guidance.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.