Instagram error 613: Calls to this API have exceeded the rate limit
Last verified against Meta for Developers - Messenger Platform error codes
Calls to this api have exceeded the rate limit.What error 613 means
Code 613 is the Graph API's "custom rate limit" error - a limit specific to the API you are calling rather than the app-wide or user-wide budgets - and subcode 2534040 is its Instagram messaging incarnation, documented on the Messenger Platform error page with the guidance "Your app has reached the rate limit. Pause API calls and try again later."
The custom limits for Instagram messaging are published per API and per content type: the Send API allows 100 calls per second per Instagram professional account for messages containing text, links, reactions and stickers, but only 10 calls per second for audio or video content; the Conversations API allows 2 calls per second per account; and private replies are capped at 100 per second for live comments and 750 per hour for comments on posts and reels. Hitting any of these produces 613/2534040 even while your app-level budget (code 4 territory) is healthy.
Because the limits are per Instagram professional account, one viral account cannot be fixed by "scaling out" your app - the ceiling moves with the account, not with you.
Why it happens
- A burst of sends to one Instagram account exceeded 100 calls per second (or 10 per second for audio/video messages).
- Conversation history reads exceeded the 2 calls per second Conversations API allowance for the account.
- Comment-to-DM automation exceeded 750 private replies per hour on posts and reels for the account.
- Fan-out logic sends to thousands of recipients in a tight loop with no per-account pacing.
- Retries of throttled calls without backoff keep the account pinned at its ceiling.
How to fix Instagram error 613
- 1Pause calls for the affected account, then resume behind a per-account rate limiter set safely below the documented ceiling.
- 2Split media sends into their own, slower queue - the 10 calls per second audio/video ceiling is a tenth of the text ceiling.
- 3For private-reply campaigns, spread replies across the hour; 750 per hour is roughly one every five seconds sustained.
- 4Replace Conversations API polling with webhook-driven state so reads stay under 2 calls per second naturally.
- 5Honor estimated_time_to_regain_access from the X-Business-Use-Case-Usage header before retrying.
How to stop it recurring
Encode the documented ceilings as configuration in your sender - text, media, reads, and private replies each with their own token bucket per Instagram account - so bursts queue instead of erroring. Alert on sustained queue depth rather than on the error itself. All of the per-API numbers, with sources, are collected in the Instagram limits reference, and the generic throttling family is described under code 4.
Official reference: Meta for Developers - Messenger Platform error codes. See all Instagram error codes or the Instagram limits and quotas.
Related codes
Error 613 - quick answers
What does Instagram error 613 mean?
Code 613 is the Graph API's "custom rate limit" error - a limit specific to the API you are calling rather than the app-wide or user-wide budgets - and subcode 2534040 is its Instagram messaging incarnation, documented on the Messenger Platform error page with the guidance "Your app has reached the rate limit.
How do I fix Instagram error 613?
1. Pause calls for the affected account, then resume behind a per-account rate limiter set safely below the documented ceiling. 2. Split media sends into their own, slower queue - the 10 calls per second audio/video ceiling is a tenth of the text ceiling. 3. For private-reply campaigns, spread replies across the hour; 750 per hour is roughly one every five seconds sustained. 4. Replace Conversations API polling with webhook-driven state so reads stay under 2 calls per…
Can I retry after error 613?
Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.
Stop debugging Instagram by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.