Document WhatsApp by product, permission, and release state

Documentation must identify the WhatsApp product first

Official business messaging and any proposed App-linked access differ in account identity, history, groups, permissions, message policy, and risk. DewEngine has neither adapter. Reference text cannot merge them under a generic API or hide scraping, evasion, anti-detection, or concealment of automation behind neutral endpoints. Every documented method needs a product ID, approved access basis, account eligibility, schema, conformance fixture, limitation, and current release state.

Explain prerequisites before authentication steps

A future guide should state the customer purpose, eligible business or account product, provider application and review status, required assets, permissions, sender identity, recipient obligations, and unsupported behaviors. Only then should it describe a hosted connection flow. Development credentials, test senders, or provider dashboard roles can expose behavior unavailable to ordinary customers, so examples must label their environment and never imply broad onboarding.

Separate conversations, messages, templates, and events

Each resource page needs native identifier scope, connected-account ownership, fields, extensions, null semantics, paging, freshness, size limits, and permissions. Official business concepts should not be generalized into App chat or group fields. Send documentation identifies category, content types, idempotency, attempt state, and provider outcomes. Event pages explain verification, authority, duplicates, ordering, coverage gaps, and customer webhook delivery.

Make policy and uncertainty actionable

Error documentation should distinguish invalid input, missing capability, recipient ineligibility, template or conversation rule, suppression, account health, provider restriction, throttle, transient outage, and indeterminate dispatch. It must say whether retry is safe and how to reconcile. Generic failures encourage customers to repeat provider-visible actions or blame recipients. Raw provider context can aid support when sanitized, but secrets and private content stay out of ordinary diagnostics.

Run samples against mocks and approved conformance accounts

Public examples should use synthetic phone numbers, message content, account IDs, and credentials. Deterministic mocks cover success, suppression, missing permission, duplicate callback, throttle, and ambiguous timeout. Connector conformance separately uses consented recipients and eligible accounts under the approved application. A code block must not display a plausible production result unless the corresponding runtime method and evidence exist in the released manifest.

Generate references from versioned capability evidence

OpenAPI, SDKs, console controls, guides, and marketing tables should consume the same product-specific manifest. Provider rule changes trigger dated review, new fixtures, changelog notes, and capability fallback when evidence no longer holds. Official business and App research remain in separate documents. Until a WhatsApp adapter clears approval and operations, the only honest API reference is an explicit unavailable state plus the evidence still required.

• Include one unsupported and one indeterminate example per write workflow
• Never let a shared WhatsApp label erase the connected product type