Choose the WhatsApp access path before designing the inbox

DewEngine treats the official WhatsApp Business Platform and QR-linked WhatsApp App sessions as separate products. The official path is research; the app-session path is decision-gated and neither is released.

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

Talk to us ↗Read technical guides →

Capability boundary

Official business access and app sessions are separate gates

WhatsApp Business Platform requires Meta business verification, app review, opt-in, templates, and quality controls. Access to standard or Business App sessions would be non-official and cannot proceed without qualified legal review and explicit product-risk approval.

Catalog status and access: WhatsApp Business Platform — research, official api; WhatsApp App accounts — decision gated, non official session
Authentication: The official track uses a verified Meta business/application setup. The app track would link a user-owned session, typically through QR pairing, but no session custody or reconnection implementation is approved.
Resources: business_conversations, messages, templates, media, chats, groups, attendees, attachments
Target actions: message.send, template.send, media.upload, chat.list, message.list, message.edit, message.delete, message.react
Target events: message.received, message.delivered, message.read, message.failed, message.sent, message.edited, message.deleted, message.reaction
Limitations and failures: Neither track is implemented; The official path and app-session path have different resources, consent, pricing, and risk; No page-level promise can apply to both account types without qualification
Release gates: WhatsApp Business Platform — Meta business verification, application review, opt-in, templates, and quality enforcement; WhatsApp App accounts — Qualified legal review and explicit product-risk approval are required before implementation or sale

Official track

Use the Business Platform for verified business messaging

The official research path centers on business conversations, templates, messages, media, opt-in, and quality enforcement. A customer must satisfy Meta's business and application requirements; DewEngine cannot remove those obligations.

App track

Keep QR-linked app access behind its decision gate

A standard or Business App session would expose the user's existing chats and groups through a non-official session. That broader inbox fit is not authorization to build or sell it; legal and product-risk approval must come first.

Conversation model

Do not merge business templates with ordinary chat actions

The normalized layer may share message and media concepts, but template sends, business conversation state, group membership, reactions, edits, and deletes belong to different capability sets. The account record must tell the product which contract applies.

Consent and policy

Make recipient permission and quality controls visible

The calling product owns opt-in, suppression, human approval, and business purpose. The connector should preserve provider feedback and block actions that the selected account type or policy state does not permit.

Failure handling

Distinguish delivery state from account health

A message can fail because of content, recipient, template, quality, connection, or provider state. Delivery and read events are available only where the selected provider path reports them, while reconnect and account restrictions need separate product states.

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.

Is this page describing the Meta Cloud API or a linked app account?+

Both are documented as separate research tracks. The official Business Platform and a decision-gated app session must never be presented as one interchangeable connector.

Can users connect a WhatsApp App account today?+

No. That access path is not implemented and remains blocked on qualified legal and explicit product-risk approval.

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 ↗