We are getting HTTP Response code of 429 indicated a client error

[kagurupr]

Hi Team,

We are from CLO Pega team, we are using webhook API call to clean up the records. While hitting the API service we are getting the failure response with the message:

"The user has sent too many requests in the given amount of time. Please refer to the Retry-After response header to wait before making a new request"

We are sending 100 request each time. Can you please any count limit there to hit the API.

URL: https://webexapis.com/v1/webhooks

Thanks!!!

[sandiban]

Hello @kagurupr,
Thanks for your patience so far!
I reviewed the Webhook API request you're making here and looks like you're working the /list-webhooks API.
But I wanted to validate some of the request parameters you're using in this API request as well as some of the Request parameter values you're using.
So, first I wanted to highlight the request parameter - "ownedBy" and looks like you're using the value "creator". This is not a valid value for this API request. The only expected value for this request parameter is - "org".
And you can only use this parameter if you're the Full Admin of your Webex Org. Otherwise you can't list down the Webhooks created under your Org.

Coming to the second parameter you've used i.e., "createdBy" as "me". This is not an allowed or, available request parameter for listing out the Webhooks.
Even the parameter - "cursor", this is also not allowed or, available request parameter for the /list-webhooks API request.
Yes, "max" is set as 100 and this should be fine!

You can actually review the /list-webhooks API documentation to understand what are the request parameter you can work with - https://developer.webex.com/messaging/docs/api/v1/webhooks/list-webhooks
Kindly review it once from your side and prepare the API request accordingly with the correct request parameters.
Let us know how it goes and if you still keep getting the same error, then kindly share the details to devsupport@webex.com and that'd raise a Support request in our queue which would be better to track it further.

Regards!
Sandip

[kagurupr]

Hi Team,

We are calling the request in the loop, we are getting the response up to 2 iteration, after that we are getting that failure response message. If you want we can have a call to understand the issue.

Please reach out to me via webex kagurupr@cisco.com.