<?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: Zetrr</title>
    <description>The latest articles on DEV Community by Zetrr (@zetrr).</description>
    <link>https://dev.to/zetrr</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%2F4247590%2Fdeb9270f-5382-43b2-b1c2-001ba38b5bf8.png</url>
      <title>DEV Community: Zetrr</title>
      <link>https://dev.to/zetrr</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zetrr"/>
    <language>en</language>
    <item>
      <title>Building on Instagram's Messaging API? The rules that decide whether your DMs survive</title>
      <dc:creator>Zetrr</dc:creator>
      <pubDate>Mon, 16 Nov 2026 11:22:04 +0000</pubDate>
      <link>https://dev.to/zetrr/building-on-instagrams-messaging-api-the-rules-that-decide-whether-your-dms-survive-1agd</link>
      <guid>https://dev.to/zetrr/building-on-instagrams-messaging-api-the-rules-that-decide-whether-your-dms-survive-1agd</guid>
      <description>&lt;h1&gt;
  
  
  Building on Instagram's Messaging API? The rules that decide whether your DMs survive
&lt;/h1&gt;

&lt;p&gt;If you have ever evaluated a DM automation tool, you have seen the same demo: connect an account, pick a keyword, watch replies go out. What the demo never shows is the layer underneath — Meta's rules for the Instagram Messaging API. Those rules decide whether an account keeps working for months or gets restricted in a week, and no copywriting can override them.&lt;/p&gt;

&lt;p&gt;This is the short version of those rules, written for anyone building on the API or choosing a tool that does.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start here: it is a conversation API, not a broadcast list
&lt;/h2&gt;

&lt;p&gt;The Messaging API gives an app access to Direct messages for a professional account — Business or Creator only. Personal accounts get nothing.&lt;/p&gt;

&lt;p&gt;And the direction of travel is fixed: the person writes first. Your app replies to someone who messaged the account, or sends a private reply to someone who commented on or mentioned it. It does not open conversations with strangers. A follow, a like, or a story view does not create a messaging window.&lt;/p&gt;

&lt;p&gt;That one fact is the fastest vendor test there is. Any tool promising cold DM outreach at scale is not running on this API.&lt;/p&gt;

&lt;h2&gt;
  
  
  The window that governs everything: 24 hours
&lt;/h2&gt;

&lt;p&gt;Once a user messages the account, you have 24 hours to reply freely — automated or human-written, including promotional content. Every new message from the user resets the clock.&lt;/p&gt;

&lt;p&gt;After the window closes, a plain send fails. The guides checked put the Send API error at code 10, subcode 2534022. Unlike WhatsApp, Instagram has no template message to reopen the conversation. The only way back in is the user writing again.&lt;/p&gt;

&lt;p&gt;So the architecture follows from the rule: build around fresh inbound messages. Keyword replies in DMs, story replies, comment keywords — those are the triggers the API actually supports. A "message everyone who ever talked to us" campaign is not a feature here; it is a sign the tool is doing something else.&lt;/p&gt;

&lt;h2&gt;
  
  
  The seven-day exception is for humans, not bots
&lt;/h2&gt;

&lt;p&gt;There is one documented extension: the &lt;code&gt;HUMAN_AGENT&lt;/code&gt; tag. It lets a real person reply for up to 7 days after the user's last message — the weekend refund question, the support thread that needs a human to look at it.&lt;/p&gt;

&lt;p&gt;Two conditions, both non-negotiable. It has to be a human typing; the tag is a declaration about who wrote the reply, and using it to push automated or bulk messages is a policy breach, charged to your account. And it is for answering one specific person who already messaged you, not a seven-day pass to message anyone.&lt;/p&gt;

&lt;p&gt;When a vendor says "we keep messaging after 24 hours," ask which tag they use and who is supposedly writing. The answer is the whole story.&lt;/p&gt;

&lt;h2&gt;
  
  
  Comments: one private reply, seven days
&lt;/h2&gt;

&lt;p&gt;Comments run on their own clock. Your app can send one private DM reply to someone who commented, within 7 days of that comment, using the comment's ID. After that single reply, the person has to respond before you can message them again. Live comments are tighter still — a private reply is only possible while the broadcast is live.&lt;/p&gt;

&lt;p&gt;This is exactly why the comment-keyword pattern ("comment GUIDE and I'll DM you the link") is the canonical safe flow: the comment opens a seven-day private-reply window, your one reply delivers the link, and once they write back the conversation continues inside the 24-hour rule.&lt;/p&gt;

&lt;h2&gt;
  
  
  The plumbing in practice
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Sending:&lt;/strong&gt; &lt;code&gt;POST /{ig-user-id}/messages&lt;/code&gt;, with the recipient identified by their Instagram-scoped ID (IGSID) — not a phone number, and not shared with WhatsApp contacts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Receiving:&lt;/strong&gt; incoming messages arrive as webhooks. Your app needs a subscribed webhook endpoint, not a poll loop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Limits on the message itself:&lt;/strong&gt; text is capped at 1,000 bytes (UTF-8).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Opening windows legitimately:&lt;/strong&gt; ice breakers — up to four suggested questions — help people start a conversation, which is the only proper way to open more windows.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this is exotic. The mistake teams make is treating the API like an email list — a store of addresses to message whenever. The state that matters is not "who is on our list" but "whose window is open right now, and what did they last say?"&lt;/p&gt;

&lt;h2&gt;
  
  
  Pacing: spread sends, pause on signals
&lt;/h2&gt;

&lt;p&gt;Meta enforces per-second limits on sends. The exact numbers are not published as a single hourly DM cap — any tool quoting one as official is guessing, so this post will not quote one either. The practical rule is the same on the creator side and the builder side: spread sends out, and back off the moment Instagram signals a limit. A tool that fires hundreds of messages in a burst gets throttled, and repeated throttling is how accounts end up restricted.&lt;/p&gt;

&lt;p&gt;If you are evaluating a tool, ask how it paces and whether it auto-pauses on limit signals. If you are building one, build the pause in first. It is not a feature to add later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five questions before you build or buy
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Does it connect through Meta's OAuth flow, with no Instagram password anywhere?&lt;/li&gt;
&lt;li&gt;Does it only message people inside an open window — 24 hours after their message, or one private reply within 7 days of their comment?&lt;/li&gt;
&lt;li&gt;Does it treat the human-agent tag as human-only, for support, never for promotion?&lt;/li&gt;
&lt;li&gt;Does it pace sends and pause on limits, instead of blasting?&lt;/li&gt;
&lt;li&gt;Does it stop messaging someone the moment they opt out?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A "no" — or a "we have a workaround" — to any of these means the tool is not built on the official API, whatever its landing page says.&lt;/p&gt;

&lt;h2&gt;
  
  
  One tool built this way
&lt;/h2&gt;

&lt;p&gt;Zetrr Automation follows exactly this model: it connects through Meta's official Instagram API — Zetrr is a Verified Meta Tech Provider — so no password is involved. It handles keyword triggers on comments and DMs, story replies, and follow-to-unlock gates, with pacing and auto-pause built in, working inside the windows above rather than around them. The free tier covers 1,000 DMs a month; Pro is ₹299 a month in India ($9 elsewhere) with the first month free.&lt;/p&gt;

&lt;p&gt;See how it works: &lt;a href="https://zetrr.com/automation" rel="noopener noreferrer"&gt;https://zetrr.com/automation&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The API's rules are not obstacles to work around. They are the reason DM automation can be a growth channel at all — the accounts that follow them are the ones that stay standing.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Facts: Meta Instagram Messaging API rules as summarised in Nov 2026 guides checked against Meta's docs — 24-hour standard window resetting on each user message; HUMAN_AGENT = human-written replies only, up to 7 days; one private reply per comment within 7 days; no cold first messages; professional (Business/Creator) accounts only; POST /{ig-user-id}/messages; webhooks; Instagram-scoped IDs; 1,000-byte text limit; no hourly DM cap quoted because Meta does not publish one. Zetrr facts: Verified Meta Tech Provider, official API, no password, Free 1,000 DMs/mo, Pro ₹299/mo India / $9 elsewhere, first month free.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>instagram</category>
      <category>api</category>
      <category>automation</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
