Repli uses Instagram Login and the documented API. That identifies the connection method, not a certification of every feature or campaign. Access levels, app mode and messaging eligibility must be checked separately.
Required account permissions, recipient eligibility and Meta limits still apply. A matching event or public reply is not proof of a delivered DM.
The account owner authorizes the access requested by the app. A browser permission screen is not proof that every feature has Advanced Access.
Permissions have separate review/access states. Comments and messaging approval does not approve publishing, insights or every business account.
A comment private reply and an ongoing inbound-DM conversation have different rules. API access does not grant arbitrary cold outreach.
Access can expire, be revoked or be restricted. Reconnection cannot bypass an app-review or account restriction.
Understand the account and requested permissions; do not share your password with Repli.
Verify current account access and test the received event and send result.
Distinguish expired account access from app-review or provider restrictions instead of promising an upgrade fixes it.
Instagram API with Instagram Login is the connection mechanism. Repli is not claiming Meta affiliation, endorsement, product certification or a ban-proof guarantee. The historical URL is retained, but “Meta-approved” is not used as a product claim.
App Review grants access for particular permissions and use cases. It is not evidence that all requested permissions, all account types or all automation mechanics are approved.
The project’s October 24 inspection recorded Advanced Access for basic account access, messages and comments; publishing and insights remained rejected/Standard. Development mode was recorded as a general rollout limitation.
Those are recorded settings, not a fresh live inspection of Meta. Confirm the current app mode, permission state and account authorization before relying on general customer availability. Buying a Repli plan or reconnecting does not change Meta’s review decision.
Private comment replies do not open an unrestricted conversation. Ongoing ordinary automated messages require an eligible inbound conversation; Live private replies have an active-broadcast restriction.
Keep failures, recipient restrictions and current provider policy visible in the workflow. No permission grant proves a message arrived, was read or produced a sale.
No blanket endorsement or certification is claimed. Official API integration and specific permission grants are different from product endorsement.
No. Reconnection can refresh account authorization but does not approve publishing/insights, change app mode or bypass Meta restrictions.
No. Repli entitlements and provider permission/review decisions are separate.
No. An initial private reply to a comment is separate from the ordinary messaging window. The person must reply before an ongoing sequence can continue, and ordinary automated messages must remain within the eligible 24-hour window.
Pricing · All features · How it works · Blog