# SonarCloud APIs

**URL:** <https://community.sonarsource.com/t/sonarcloud-apis/143237>\
**Category:** SonarQube Cloud\
**Tags:** api, sonarqube-cloud\
**Created:** [June 23, 2025, 6:17am UTC](https://community.sonarsource.com/t/sonarcloud-apis/143237 "2025-06-23T06:17:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Prathiksha\_P](https://avatars.discourse-cdn.com/v4/letter/p/e56c9b/32.png) [@Prathiksha\_P](https://community.sonarsource.com/u/Prathiksha_P)\
**Post date:** [June 23, 2025, 6:17am UTC](https://community.sonarsource.com/t/sonarcloud-apis/143237/1 "2025-06-23T06:17:41Z")

</div>

We are currently planning to integrate SonarCloud APIs as part of our Scan Vault implementation. To ensure smooth and efficient integration, could you please help clarify the following:Which API we can use ?

- Is there any **API throttling or rate limiting** in place?
- If yes, what is the **maximum number of requests allowed** (per minute/hour/day)?
- Are there any **differences in rate limits** based on the type of authentication used (e.g., token vs. OAuth)?
- Are there any **best practices or recommendations** to avoid hitting the rate limits?
- Is there a way to **monitor or receive alerts** when approaching the rate limit?

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [June 24, 2025, 8:17am UTC](https://community.sonarsource.com/t/sonarcloud-apis/143237/2 "2025-06-24T08:17:33Z")

</div>

SonarQube Cloud enforces [API rate limiting](https://docs.sonarsource.com/sonarqube-cloud/advanced-setup/web-api/#api-rate-limiting) to prevent abuse. Although specific thresholds aren’t published, keeping your requests below 1,000 per minute should avoid any issues. These limits apply regardless of authentication method. If you exceed the rate limit, you’ll receive HTTP 429 response codes.