# Instagram API rate-limit calculator: 200 DMs/hour cap & viral Reel queuing (2026)

> Calculate when your viral Instagram Reel will hit Meta's 200 automated DMs/hour API limit and how smart queuing prevents lost leads.

- **Interactive Tool URL:** https://rapiddm.com/tools/instagram-api-rate-limit-calculator
- **Author:** RapidDM
- **Published:** 2026-09-28T09:15:00+05:30
- **Updated:** 2026-09-28T09:15:00+05:30
- **Tags:** Meta Graph API, Rate limits, Viral Reels, Technical calculator

---

In October 2024, Meta reduced the Instagram Graph API rate limit for automated messaging to 200 automated API calls per Instagram account per rolling hour. That limit remains in place across all approved platforms in 2026.

For everyday posts getting 30 to 80 comments an hour, you will never notice the ceiling. When a Reel catches the algorithm and pulls 500 to 3,000 comments per hour, that 200-call limit decides whether you capture every commenter or drop 80% of them.

## What counts toward the 200 calls/hour limit?

Every outbound action your automation takes through the Instagram Graph API draws from your account's hourly quota:

| Automation step | Graph API endpoint | Quota impact per commenter |
| --- | --- | --- |
| Initial Private Reply DM | POST /<IG_ID>/messages (comment_id) | 1.0 messaging call |
| Public comment auto-reply | POST /<COMMENT_ID>/replies | ~0.5 weighted app/account load |
| Follow-to-Unlock verification + link DM | GET friendship + POST /<IG_ID>/messages | ~0.7 weighted call (when button tapped) |

## How RapidDM prevents dropped DMs during viral spikes

Basic automation scripts fire an HTTP request to Meta the moment a comment webhook arrives. Once your account crosses 200 calls in a 60-minute window, Meta returns Error Code `613` (`Calls to this api have exceeded the rate limit`) and drops the message.

RapidDM handles viral traffic spikes with a per-account Redis and BullMQ token-bucket queue:

- **Instant delivery below 200 calls/hour:** When comment traffic sits under the hourly cap, webhooks process immediately with a 2 to 5 second human-like delay.
- **Overflow buffering above 200 calls/hour:** Instead of hitting Meta's API and failing, comment #201 and beyond sit in an ordered queue tied to your Instagram account ID.
- **Safe pacing inside the 7-day Private Reply window:** Because Meta's Private Reply API accepts responses for up to 7 days (168 hours) after a comment is posted, RapidDM drains a 2,000-comment overnight burst automatically over the next 10 to 15 hours without losing a single lead.

Read our full breakdown on [Instagram API Error 2534022 and the 7-day Private Reply window](/blog/instagram-error-2534022-private-reply-window-expired-fix) for more detail on how Meta's time windows work.

## Frequently asked questions

### What is Meta's official Instagram DM automation rate limit in 2026?

Since October 2024, Meta enforces a ceiling of 200 automated API calls per Instagram Professional account per hour for outbound messaging. Human replies sent manually inside the Instagram app do not count against this API quota.

### What happens if my viral Reel gets 1,000 comments in an hour?

If your tool does not use a smart rate-limit queue, Meta rejects calls #201 through #1,000 with HTTP 429 / Error Code 613 (Calls to this api have exceeded the rate limit), and those 800 commenters never receive your DM. RapidDM queues overflow comments in Redis/BullMQ and paces delivery at 200 calls/hour until all 1,000 DMs are delivered.

### How long do I have to send an automated DM after someone comments?

Meta's Private Reply API grants a 7-day (168-hour) window from the exact timestamp a user comments on an organic post or Reel. As long as your queued DM dispatches within 7 days, Meta delivers it without throwing Error 2534022.

### Do Follow-to-Unlock flows use more than one API call per commenter?

Yes. Sending the initial Follow-to-Unlock card uses 1 API call. When the user taps the 'I'm following' button, verifying their follower status and dispatching the final link uses another call.