<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: We are getting HTTP Response code of 429 indicated a client error in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/we-are-getting-http-response-code-of-429-indicated-a-client/m-p/5293564#M4326</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1880392"&gt;@kagurupr&lt;/a&gt;,&lt;BR /&gt;Thanks for your patience so far!&lt;BR /&gt;I reviewed the Webhook API request you're making here and looks like you're working the &lt;A href="https://developer.webex.com/messaging/docs/api/v1/webhooks/list-webhooks" target="_blank"&gt;/list-webhooks&lt;/A&gt; API.&lt;BR /&gt;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.&lt;BR /&gt;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".&lt;BR /&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;BR /&gt;Even the parameter - "cursor", this is also not allowed or, available request parameter for the /list-webhooks API request.&lt;BR /&gt;Yes, "max" is set as 100 and this should be fine!&lt;/P&gt;
&lt;P&gt;You can actually review the /list-webhooks API documentation to understand what are the request parameter you can work with -&amp;nbsp;&lt;A href="https://developer.webex.com/messaging/docs/api/v1/webhooks/list-webhooks" target="_blank"&gt;https://developer.webex.com/messaging/docs/api/v1/webhooks/list-webhooks&lt;/A&gt;&lt;BR /&gt;Kindly review it once from your side and prepare the API request accordingly with the correct request parameters.&lt;BR /&gt;Let us know how it goes and if you still keep getting the same error, then kindly share the details to &lt;A href="mailto:devsupport@webex.com" target="_blank"&gt;devsupport@webex.com&lt;/A&gt;&amp;nbsp;and that'd raise a Support request in our queue which would be better to track it further.&lt;/P&gt;
&lt;P&gt;Regards!&lt;BR /&gt;Sandip&lt;/P&gt;</description>
    <pubDate>Sun, 25 May 2025 13:18:51 GMT</pubDate>
    <dc:creator>sandiban</dc:creator>
    <dc:date>2025-05-25T13:18:51Z</dc:date>
    <item>
      <title>We are getting HTTP Response code of 429 indicated a client error</title>
      <link>https://community.cisco.com/t5/webex-for-developers/we-are-getting-http-response-code-of-429-indicated-a-client/m-p/5293377#M4321</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;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:&lt;/P&gt;
&lt;P&gt;"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"&lt;/P&gt;
&lt;P&gt;We are sending 100 request each time. Can you please any count limit there to hit the API.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;URL: &lt;A href="https://webexapis.com/v1/webhooks" target="_blank" rel="noopener"&gt;https://webexapis.com/v1/webhooks&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Thanks!!!&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 19:05:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/we-are-getting-http-response-code-of-429-indicated-a-client/m-p/5293377#M4321</guid>
      <dc:creator>kagurupr</dc:creator>
      <dc:date>2025-05-23T19:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: We are getting HTTP Response code of 429 indicated a client error</title>
      <link>https://community.cisco.com/t5/webex-for-developers/we-are-getting-http-response-code-of-429-indicated-a-client/m-p/5293564#M4326</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1880392"&gt;@kagurupr&lt;/a&gt;,&lt;BR /&gt;Thanks for your patience so far!&lt;BR /&gt;I reviewed the Webhook API request you're making here and looks like you're working the &lt;A href="https://developer.webex.com/messaging/docs/api/v1/webhooks/list-webhooks" target="_blank"&gt;/list-webhooks&lt;/A&gt; API.&lt;BR /&gt;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.&lt;BR /&gt;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".&lt;BR /&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;BR /&gt;Even the parameter - "cursor", this is also not allowed or, available request parameter for the /list-webhooks API request.&lt;BR /&gt;Yes, "max" is set as 100 and this should be fine!&lt;/P&gt;
&lt;P&gt;You can actually review the /list-webhooks API documentation to understand what are the request parameter you can work with -&amp;nbsp;&lt;A href="https://developer.webex.com/messaging/docs/api/v1/webhooks/list-webhooks" target="_blank"&gt;https://developer.webex.com/messaging/docs/api/v1/webhooks/list-webhooks&lt;/A&gt;&lt;BR /&gt;Kindly review it once from your side and prepare the API request accordingly with the correct request parameters.&lt;BR /&gt;Let us know how it goes and if you still keep getting the same error, then kindly share the details to &lt;A href="mailto:devsupport@webex.com" target="_blank"&gt;devsupport@webex.com&lt;/A&gt;&amp;nbsp;and that'd raise a Support request in our queue which would be better to track it further.&lt;/P&gt;
&lt;P&gt;Regards!&lt;BR /&gt;Sandip&lt;/P&gt;</description>
      <pubDate>Sun, 25 May 2025 13:18:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/we-are-getting-http-response-code-of-429-indicated-a-client/m-p/5293564#M4326</guid>
      <dc:creator>sandiban</dc:creator>
      <dc:date>2025-05-25T13:18:51Z</dc:date>
    </item>
    <item>
      <title>Re: We are getting HTTP Response code of 429 indicated a client error</title>
      <link>https://community.cisco.com/t5/webex-for-developers/we-are-getting-http-response-code-of-429-indicated-a-client/m-p/5294010#M4333</link>
      <description>Hi Team,&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Please reach out to me via webex kagurupr@cisco.com.&lt;BR /&gt;</description>
      <pubDate>Tue, 27 May 2025 08:21:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/we-are-getting-http-response-code-of-429-indicated-a-client/m-p/5294010#M4333</guid>
      <dc:creator>kagurupr</dc:creator>
      <dc:date>2025-05-27T08:21:56Z</dc:date>
    </item>
  </channel>
</rss>

