USING SNYK
API rate limit control
Azure DevOps
Azure DevOps has a unique way of limiting the API call rate with their own "TSTU" concept as described in this guide.
The
snyk-scm-contributors-count tool applies a strict limit of a maximum of two calls per second to deal with the rate limit.Bitbucket Cloud
On Bitbucket Cloud, the API rate limit is 1,000 calls per hour for authenticated users as described in this guide.
The
snyk-scm-contributors-count tool applies a strict limit of a maximum of 1,000 calls per hour to deal with the rate limit and an additional regulating mechanism to deal with 429 responses ("too many calls").Bitbucket Server
On Bitbucket Server, the system admin has full control of the API rate limiting as described in this guide.
The
snyk-scm-contributors-count tool applies a moderate limit of a max 1000 calls per hour and additional regulating mechanism to deal with 429 responses ("too many calls")GitHub
On GithHub, the API rate limit is 5,000 calls per hour for authenticated users as described in this guide.
The
snyk-scm-contributors-count tool applies a strict limit of a maximum of 4,500 calls per hour to deal with the rate limit and an additional regulating mechanism to deal with 429 responses ("too many calls").GitHub Enterprise
On Github Enterprise, the API rate limit is 15,000 calls per hour for authenticated users as described in this guide.
The
snyk-scm-contributors-count tool applies a strict limit of a maximum of 3 calls per second which amounts to 10,800 calls per hour, to deal with the rate limit and an additional regulating mechanism to deal with 429 responses ("too many calls").GitLab and GitLab Server
The
snyk-scm-contributors-count tool applies a strict limit of a maximum of 120 calls per minute to deal with the rate limit and an additional regulating mechanism to deal with 429 responses ("too many calls").Last modified 14d ago
Export as PDF
Copy link
Edit on GitHub