Rate Limiting

Degreed limits the number of calls a single API client can make to 70 requests per minute (rpm). If you exceed the limit, a 429 Too Many Requests response is returned with a Retry-After header that specifies the amount of time to wait before making another request.

All other responses from the API contain the following headers:

X-Rate-Limit-LimitThe rate limit period (for example, 1m, 12h, 1d).
X-Rate-Limit-RemainingThe number of requests remaining.
X-Rate-Limit-ResetUTC date and time (ISO 8601) when the limits resets.

The following is an example response with rate limiting headers:

HTTP/1.1 200 OK
X-Rate-Limit-Limit: 1m
X-Rate-Limit-Remaining: 69
X-Rate-Limit-Reset: 2021-10-26T20:39:22.1494434Z

To avoid common causes of rate limiting issues, follow these best practices:

  • Use the ?limit parameter to increase the number of resources returned per request.

  • Use filter parameters to return subsets of data that identify changes rather than complete data sets. For example, for some endpoints, you can make an API call that filters data by date to retrieve only new data rather than retrieve all data.
    This sample request uses a date filter:

    GET https://betatest.degreed.com/api/v2/content?filter%5Bstart_date%5D=2020-01-01
  • Process jobs slowly at off-hours if they are large but not time-sensitive.

If you require a higher rate limit, contact your Degreed Technical Solutions Specialist.

What’s Next