- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2016 06:16 AM
Hi Sunil,
Can you help me understand what you mean by "rate limits"? I'm not sure I understand. It sounds like you are asking about costs involved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2016 06:26 AM
No , I am not concerned with costs here.
I want to know details regarding API limits i.e. is there any message displayed in the response when I exceed the limit on API like in some of the applications we get message as HTTP429 Too Many Requests once API limits are reached.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2016 06:30 AM
Thank you for the clarification. I have not heard of any API limitations on too many requests.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2017 12:35 PM
Sunil,
I found this and thought it might be useful:
"The number of requests allowed in the default (UI) semaphore pool is 16 processing (number of semaphores) and 150 in the queue. After the queue maximum is reached, the system will not allow any more."
I found this here: https://hi.service-now.com/kb_view.do?sysparm_article=KB0594813
Hope this helps you or someone else. It helped me.
Kenny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2024 09:56 AM
Yes, for Inbound REST calls the default rate limit is 10,000 request per hour, but you can change it in sys_rate_limit_rules table.
Please mark this solution as helpful if it solves your issue.
Thanks,
Amitoj Wadhera