Separate official Instagram messaging from broader account access

DewEngine's official research path is limited to eligible professional accounts and declared conversation, message, profile, and media resources. Broader session-based posts or relationship actions are decision-gated and not part of that official surface.

Decision gate closed. This access path is neither approved nor implemented; no provider action is available.

Talk to us ↗Read technical guides →

Capability boundary

Instagram has one planned official path and one blocked broader path

The official provider requires Meta application review and professional-account eligibility. A wider account session would be non-official and cannot proceed without qualified legal review and explicit product-risk approval.

Catalog status and access: Instagram professional accounts — planned, official api; Broader Instagram account access — decision gated, non official session
Authentication: Official access must use the eligible Meta account and reviewed application. Broader session authorization has no approved connection implementation and must remain distinguishable in every account and capability response.
Resources: conversations, messages, profiles, media, posts, relations
Target actions: chat.list, message.list, message.send, profile.get, post.create, relation.follow
Target events: message.received, message.sent, account.status
Limitations and failures: No Instagram connector is implemented; Story replies, read state, comments, and generic engagement events are not declared; Professional-account eligibility and broader session policy cannot be hidden behind one feature list
Release gates: Instagram professional accounts — Meta application review and professional-account eligibility; Broader Instagram account access — Qualified legal review and explicit product-risk approval are required before implementation or sale

Official inbox

Design around eligible professional conversations

The planned official track covers conversation listing, message listing and sending, profile context, and media where the reviewed Meta application and connected professional account permit them. Unsupported account types should fail eligibility before a workflow is configured.

Broader account access

Keep posts and relationship actions behind a separate gate

The catalog records a non-official session research path for wider posts and relationship actions. Those features must not be implied by the official inbox connector and remain blocked pending legal and product-risk approval.

Resource model

Bind media and profiles to the conversation that exposed them

A normalized message can reference media and participant profiles while retaining native conversation, sender, and asset identifiers. The product should not infer access to unrelated profile or content data from permission to read an inbox.

Sending

Validate capability and provider state before a reply

A target reply command needs the connected account, conversation, supported content type, and durable intent. Provider acceptance becomes a sent event only when backed by the declared provider response; read or engagement claims are outside the current catalog.

Recovery

Expose eligibility, review, token, and policy failures

Professional-account changes, consent loss, application review state, throttling, and decision-gated session restrictions need distinct errors. Reconnection cannot be a generic retry when the account is no longer eligible for the selected access path.

Decision-gated contract

Review the policy boundary before implementation.

This shape documents a blocked product boundary. Legal, provider, and product-risk gates must clear before implementation or sale; it is not callable.

Explicit connected-account ownership
Stable public resource identifiers
Truthful provider outcome state
Release status beside every capability

Illustrative shapeDecision-gated · not callable

const unreleasedContract = {
  resource: "message",
  account_id: "acc_example",
  provider: "target_provider",
  availability: "not_implemented"
} as const;

No approved connector · no provider request

Questions

Before you build.

Will the official connector work with every Instagram account?+

No. The planned official path is limited by Meta application review and professional-account eligibility.

Are posts and relationship actions included in the official inbox plan?+

No. Those belong to a separate, non-official session target that remains decision-gated.

Build with us

Does this match the workflow your users need?

DewEngine is in development. Real use cases decide what ships first.

Share your use case ↗