Getting 429 Error with service now

RFJ1
Tera Contributor

Hi,

 

We are receiving 429 HTTP error code while making API calls to our instance from Third Party integration, the ask is to update a change request but we get this 429 error. I've read enough to know that 429 indicates too many requests being made and the nodes are basically full not to process anymore but I want to know how is this limit decided? How many API calls from a particular integration would make it too much and throw 429? Is there a place where we can find it or define it?

 

Would be great if I can find some help on this.

 

Thanks in advance.

5 REPLIES 5

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @RFJ1 

 

You can log a case with Now Support for this. 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Community Alums
Not applicable

Hi @RFJ1 ,

Please check this KB article 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0635398

 

Please mark correct and helpful if this works for you

 

Thanks and Regards 

Sarthak

VadimJ
Tera Contributor

I was playing with the NVD integration for Vulnerability Response on MyPD and specifically for this code: 
"Error: Invalid response code received from NVD: 429" - all I had to do to use different API key and it started working again. No changes to config itself (it was all OOTB) just replaced the key (requested from the NVD)

Anand Kumar P
Giga Patron
Giga Patron

Hi @RFJ1 ,

if you're rate limiting your service, you'll respond with 429 too many requests for users who have exceeded the rate limit. requests reach an instance, each node maintains a rate limit count per user. Every 30 seconds, the count is committed to the database. As a result, a rate limit rule may not take effect for up to 30 seconds.

Refer below link:

https://www.servicenow.com/community/developer-blog/enforces-rate-limits-on-your-api-endpoints-to-pr...

 

If my response helped, please mark it as the accepted solution and give a thumbs up👍.
Thanks,
Anand