Default REST api rate limit for users

George S
Kilo Explorer

‎11-13-2020 04:43 AM

Does anybody know what, if any, the inbound REST api rate limit is for Service now instances? 

I've seen many comments about how to implement rate limits per user.  If the rate limit is not implemented, what are the risks/performance impacts to the instance? 

Let's say an application is calling a Service Now endpoint to fetch 10M incidents using a fetch size of 1,000 records per call.  While these repeated fetches are made, would users of the instance feel a performance impact? 

Also, is there any event that would cause ServiceNow to return 429 errors when a rate limit was not manually implemented for the user making the REST calls?

Labels:
0 Helpfuls
  • 2,486 Views
1 REPLY 1

Brad Tilton
ServiceNow Employee
ServiceNow Employee

‎11-13-2020 05:46 AM

Hi George, I'm not sure if this answers all your questions specifically, but it's helpful to know that each instance has sets of semaphores (workers) dedicated to things like rest, soap, UI so that you might tie up the REST semaphores but there would still be some available for users interacting through the UI. Here is a pretty good hi kb article that talks about it: https://hi.service-now.com/kb_view.do?sysparm_article=KB0635977