Changelog

Planned. This entry is a roadmap, not a release. Where an item has an API contract — the communities, business-catalog and interactive-message endpoints — it is already published in the OpenAPI document with x-phase: 2, so integrations can be written against it today; until it ships it answers 501 feature_not_available. Breaking changes to anything already released are announced here before they go live.

Planned

• Official Cloud API channel type, so an account can run a Meta-approved number beside its linked ones through the same endpoints and webhooks.
• Team members and workspaces: more than one login per account, with roles.
• Partner API and white-label: create and manage channels for your own customers under your brand.
• Interactive and carousel messages, if and when the engines can produce them reliably on current WhatsApp clients.
• Communities: create, link and unlink groups, list subgroups and participants.
• Business catalog: profile editing, products and orders on Business accounts.
• Non-English pages: the documentation and guides in Spanish and Brazilian Portuguese first.
• Typed SDK packages for npm, pip and Composer, generated from the same OpenAPI document as this reference.
• An MCP server and agent skill, so an assistant can drive a channel through the documented operations.

The first release of Wapito: a channel you can link to a WhatsApp number, a Bearer token, the REST API and signed webhooks. It is open to invited accounts while the engine is under observation.

In this build

• Channels: create, link by pairing code or QR, restart, log out and delete, with live status in the dashboard.
• Messaging: text, image, video, audio, voice, document, sticker, location, contact, poll and reaction, plus edit, delete, mark-as-read and — on the NOWEB engine — forward and star.
• Groups: create, list, update the subject and description, settings, icon, invite links, join by invite, participants, admins, join requests and leave.
• WhatsApp Channels (newsletters): create, list, find, read and delete, and post to one with any send endpoint. Stories: text, media and audio.
• Contacts and presence: list and get contacts, bulk number checks, profile pictures, LID resolution in both directions, and online, typing and recording indicators.
• Media: upload once and send many times, inbound media copied out of the engine and served on signed links for 24 hours on Sandbox and 7 days on Premium.
• Webhooks: two endpoints per channel on Sandbox and five on Premium, with event filters, retries with backoff, a per-endpoint circuit breaker, a test endpoint and an X-Wapito-Signature header on every delivery.
• Anti-ban controls on every plan: send pacing with jitter, typing simulation, the warm-up ladder, the cold-send guard, timelock detection and a ban detector that reports through the channel event.
• Dashboard: Connect, Settings, API, Logs and Usage tabs, with one-time token reveal and rotation.

Known limits

• QR linking of a new device has been unreliable since WhatsApp changed device linking in mid-2026, so the pairing code is the primary path and QR is the fallback.
• Labels, business profile editing and catalogue endpoints need the NOWEB engine and are not enabled on preview accounts yet.
• Communities, business catalog, interactive and carousel messages, group deletion, story listing and contact blocking are published in the OpenAPI document for contract stability and answer 501 feature_not_available; the 0.2.0 entry lists them.