Organizations that send many requests quickly may see error responses as status code 429.
Note that individual APIs may have their API Rate Limit and will be documented as such. Otherwise, the following default rate limits apply.
Method | Request Limit | Concurrency Limit |
|---|---|---|
GET | 10 Requests per second | Not Applicable |
POST | 10 Requests per second | Not Applicable |
PUT | 10 Requests per second | Not Applicable |
PATCH | 10 Requests per second | Not Applicable |
DELETE | 10 Requests per second | Not Applicable |
See Default Rate Limit to view Reporting API limits and how limits are handled.
How to check check current API rate limit
The best way they can track current API limit/usage would be the moment you are using an API itself. Because the moment you’ve used an API, the remaining limit and their total limit is in the response headers.
Ratelimit-Limit-Second
Ratelimit-Remaining-SecondSee Rate Limits to learn more.
In Postman you would see it in the headers tab, if they are using anything else other than Postman, then they should still see it in the response headers of the tool they are using
.png?sv=2022-11-02&spr=https&st=2025-11-25T12%3A57%3A14Z&se=2025-11-25T13%3A08%3A14Z&sr=c&sp=r&sig=FE6lyeMRi5qrjk6ZUOsGnV12lYmumLu4CzgdN5AjEfI%3D)
Report-wise, it would be to track your own API calls and compile it and work on the timeframes if you are hitting the default 10 API calls per second.