<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rohan Singh</title>
    <description>The latest articles on DEV Community by Rohan Singh (@rohan_singh_2e5b8c9749af4).</description>
    <link>https://dev.to/rohan_singh_2e5b8c9749af4</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4218810%2F43244d76-02ca-484c-95b6-25cb20b077d3.png</url>
      <title>DEV Community: Rohan Singh</title>
      <link>https://dev.to/rohan_singh_2e5b8c9749af4</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rohan_singh_2e5b8c9749af4"/>
    <language>en</language>
    <item>
      <title>WhatsApp Business API for Developers: What to Know Before You Build</title>
      <dc:creator>Rohan Singh</dc:creator>
      <pubDate>Sat, 31 Oct 2026 10:21:30 +0000</pubDate>
      <link>https://dev.to/rohan_singh_2e5b8c9749af4/whatsapp-business-api-for-developers-what-to-know-before-you-build-bdk</link>
      <guid>https://dev.to/rohan_singh_2e5b8c9749af4/whatsapp-business-api-for-developers-what-to-know-before-you-build-bdk</guid>
      <description>&lt;p&gt;So someone on your team says “can we just add WhatsApp to the product?” and you say sure, how hard can it be. I said the same thing. It’s not hard, but there’s more to it than sending a POST request.&lt;/p&gt;

&lt;p&gt;First question: build directly on Meta’s API or use a platform on top of it? Hold that thought, a few basics first.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpsp4dgtrmona2z6lbfs8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpsp4dgtrmona2z6lbfs8.png" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;br&gt;
The basics&lt;/p&gt;

&lt;p&gt;The WhatsApp Business API lets software send and receive messages for a business. The regular Business app is meant for one person on one phone, while the API is for teams, automation and integrations.&lt;/p&gt;

&lt;p&gt;Stuff that will bite you&lt;br&gt;
Opt-in. You can only message people who agreed to hear from you. No shortcuts here.&lt;br&gt;
Templates. Business-initiated messages usually need pre-approved templates, and approval can take a while, so don’t leave it for launch week.&lt;br&gt;
The 24-hour window. After a customer messages you, you can reply more freely for a limited time. Outside that, it’s templates again.&lt;br&gt;
Webhooks. Incoming messages and delivery status come in as webhook events. Your endpoint needs to be reliable, and yes, you’ll get duplicates.&lt;br&gt;
The inbox problem. If humans reply too, you need a UI so two agents don’t answer the same chat. This one is easy to underestimate.&lt;br&gt;
Build or buy?&lt;/p&gt;

&lt;p&gt;Building directly gives you full control. It also means you own the inbox UI, campaign tools, retries, template management and chatbot flows. That’s a lot of work that isn’t your actual product.&lt;/p&gt;

&lt;p&gt;A platform covers most of it. Trafficaro is one example, with campaigns, a shared inbox, chatbots and an AI voice agent on Meta’s official API, plus rupee plans and a free plan. I’d compare a few before picking: pricing, markup on Meta’s charges, and how good the docs and support really are.&lt;/p&gt;

&lt;p&gt;Quick checklist&lt;br&gt;
 Confirm opt-in for every contact&lt;br&gt;
 Get templates approved early&lt;br&gt;
 Make webhook handling idempotent&lt;br&gt;
 Plan a human handoff for the chatbot&lt;br&gt;
 Don’t use unofficial libraries on a production number (you can lose the number)&lt;/p&gt;

</description>
      <category>whatsapp</category>
      <category>api</category>
      <category>automation</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
