Instagram error 100: Business blocked from the Instagram Messaging API
Last verified against Meta for Developers - Messenger Platform error codes
The business has been blocked from sending messages via the IG Messaging APIWhat error 100 means
Subcode 2534029 is the account-level enforcement error: Meta has blocked this business from sending through the Instagram messaging API. The documented guidance is to "check to make sure you do not have any policy violations that must be rectified before you can send messages using the Messenger Platform." Unlike the per-recipient refusals (551, 200/1545041), this one fails for every recipient, while tokens, webhooks, and the rest of the integration look perfectly healthy.
Blocks of this kind follow policy problems: messaging outside the allowed window at scale, misusing the human_agent tag on automated messages, spam-like volume or content, or accumulated user reports and blocks. It is enforcement, not a bug, and the resolution path runs through Meta - reviewing policy status in the App Dashboard and Business Support Home, fixing the violating behavior, and appealing where an appeal is offered.
Why it happens
- Automation violated the messaging window policy at scale, or stamped automated sends with the human_agent tag.
- Spam-pattern behavior: unsolicited broadcasts, aggressive follow-ups, or content generating user reports and blocks.
- Platform-policy violations flagged on the app, the Page, or the business account.
- Repeated ignoring of throttling and refusal errors, which compounds into integrity enforcement.
How to fix Instagram error 100
- 1Check Business Support Home (business.facebook.com/business-support-home) and the App Dashboard for violation notices, restrictions, and appeal options.
- 2Stop the offending automation entirely before appealing - an active violation makes appeals pointless.
- 3Audit window compliance and human_agent usage in your send logs; fix the code paths that violated policy.
- 4Follow the appeal or remediation flow Meta presents; there is no API parameter that lifts the block.
- 5After reinstatement, ramp volume gradually with strict window enforcement and consent-based audiences.
How to stop it recurring
Enforce the messaging window in code, reserve the human_agent tag for verified human replies, and treat rising block rates (551) as an early-warning metric with an owner. Keep audiences strictly opt-in. The policy surface - window, tags, and what Instagram deliberately does not offer (no re-engagement templates) - is summarized in the limits reference, and the escalation ladder is discussed in the troubleshooting guide.
Official reference: Meta for Developers - Messenger Platform error codes. See all Instagram error codes or the Instagram limits and quotas.
Related codes
- 551: This person isn't receiving messages from you right nowUser Block Error: This person isn't receiving messages from you right now.
- 10: Message sent outside of allowed windowThis message is sent outside of allowed window.
- 200: Account owner has disabled access to direct messagesThe account owner has disabled access to instagram direct messages.
- 100: Action invalid - app is not the thread ownerThe action is invalid since it's not the thread owner.
Error 100 - quick answers
What does Instagram error 100 mean?
Subcode 2534029 is the account-level enforcement error: Meta has blocked this business from sending through the Instagram messaging API.
How do I fix Instagram error 100?
1. Check Business Support Home (business.facebook.com/business-support-home) and the App Dashboard for violation notices, restrictions, and appeal options. 2. Stop the offending automation entirely before appealing - an active violation makes appeals pointless. 3. Audit window compliance and human_agent usage in your send logs; fix the code paths that violated policy. 4. Follow the appeal or remediation flow Meta presents; there is no API parameter that lifts the block. 5.…
Stop debugging Instagram by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.