<?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: Campaign messages in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/campaign-messages/m-p/5322494#M4493</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/762837"&gt;@sharatb&lt;/a&gt;&amp;nbsp;if you are talking about the &lt;A href="https://developer.webex.com/messaging/docs/api/v1/messages" target="_blank"&gt;Messages API&lt;/A&gt;&amp;nbsp;then you will need to deal with potential rate limiting. Best way to deal with it is to implement a logic for handling 429 responses. We have a good blog post for that here&amp;nbsp;&lt;A href="https://developer.webex.com/blog/rate-limiting-and-the-webex-api" target="_blank"&gt;https://developer.webex.com/blog/rate-limiting-and-the-webex-api&lt;/A&gt;&amp;nbsp;and further resources here&amp;nbsp;&lt;A href="https://developer.webex.com/messaging/docs/basics#rate-limiting" target="_blank"&gt;https://developer.webex.com/messaging/docs/basics#rate-limiting&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Aug 2025 13:31:06 GMT</pubDate>
    <dc:creator>Janos Benyovszki</dc:creator>
    <dc:date>2025-08-20T13:31:06Z</dc:date>
    <item>
      <title>Campaign messages</title>
      <link>https://community.cisco.com/t5/webex-for-developers/campaign-messages/m-p/5322027#M4490</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I need to send campaign messages to around 90k users. Are there any API limits per user? If so, what is the limit?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can I send the messages in batch via Webex APIs or does it have to be one by one?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 19 Aug 2025 16:18:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/campaign-messages/m-p/5322027#M4490</guid>
      <dc:creator>sharatb</dc:creator>
      <dc:date>2025-08-19T16:18:02Z</dc:date>
    </item>
    <item>
      <title>Re: Campaign messages</title>
      <link>https://community.cisco.com/t5/webex-for-developers/campaign-messages/m-p/5322494#M4493</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/762837"&gt;@sharatb&lt;/a&gt;&amp;nbsp;if you are talking about the &lt;A href="https://developer.webex.com/messaging/docs/api/v1/messages" target="_blank"&gt;Messages API&lt;/A&gt;&amp;nbsp;then you will need to deal with potential rate limiting. Best way to deal with it is to implement a logic for handling 429 responses. We have a good blog post for that here&amp;nbsp;&lt;A href="https://developer.webex.com/blog/rate-limiting-and-the-webex-api" target="_blank"&gt;https://developer.webex.com/blog/rate-limiting-and-the-webex-api&lt;/A&gt;&amp;nbsp;and further resources here&amp;nbsp;&lt;A href="https://developer.webex.com/messaging/docs/basics#rate-limiting" target="_blank"&gt;https://developer.webex.com/messaging/docs/basics#rate-limiting&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2025 13:31:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/campaign-messages/m-p/5322494#M4493</guid>
      <dc:creator>Janos Benyovszki</dc:creator>
      <dc:date>2025-08-20T13:31:06Z</dc:date>
    </item>
  </channel>
</rss>

