New features and changes, newest first. The API follows a versioning policy: v1 stays available for at least two years after a v2 is announced.
Order-and-Pay: a shop and takeaway ordering on WhatsApp
2026-11-13 in the next release - A product catalog for your number: categories, products with pictures, variants (size, colour) with their own stock, options and extras, allergens. Up to 10,000 products; bulk upload and download as CSV or Excel, also files from Shopify, WooCommerce and Square, with a check before anything changes and an undo.
- An order page made for you at /shop/<your name>: search, filters by your own attributes, tags and price, a cart, pickup or delivery with the last addresses one tap away, delivery costs by flat fee, zone or order value, "as soon as possible" or a time slot, discount codes and tips.
- Paying online with your own Stripe or PayPal account (cards, Apple Pay, Google Pay, PayPal, with the items listed on the payment page), or at pickup / on delivery.
- In the chat: a customer writes "menu" and gets a button to the order page that already knows who they are; "status", "cancel order", "again" and product questions are answered; the confirmation and the "ready" message carry a pickup QR code.
- Orders on the dashboard with a sound for new ones, an e-mail for every order, and the day's figures by e-mail after closing time. Stock is counted down the moment an order is placed, with a history of what sold, when and to whom.
- A counter app at /counter for staff phones: the open orders, scan the customer's code, see PAID or TO PAY, hand over. Every hand-over is recorded with who, when, on which phone and how the customer was identified. Reports with a hand-over log.
Calendar app, online booking page, payments
2026-11-11 in the next release - Calendar app at /calendar: day, week, month and list views made for tablets and phones. Book, move, cancel, block time, write notes, see customers, run meeting polls.
- Calendar team: invite people to the calendar only, as administrator, staff or viewer, with options to show only their own entries and to hide customer contact details.
- Online booking page at /book/<your name> for customers on a phone, with a personal link tag {booking_link} for your WhatsApp texts, an embed snippet, a QR code and a calendar subscription feed (.ics). A customer we do not know yet confirms through WhatsApp.
- More event types: group events with a number of places, events where everyone attends, round robin, and polls.
- Payments with your own Stripe or PayPal account (no fee from app2email): prices, deposits, coupons, prepaid packages, one-off payment links, refunds, automatic cancel of unpaid bookings.
- Customer e-mails for bookings and extra notification rules; branding, cancellation policy and redirect for the booking page; deleting a customer's booking data and automatic deletion after a number of days.
- API, webhook events and MCP tools for the calendar, notes, links, holds, payments, packages, customers and polls.
Bookings on WhatsApp Flows; the Inbox
2026-11-06 in the next release - Appointment booking inside WhatsApp: a customer writes "book" and picks a service, a day and a time in a WhatsApp Flow; the booking is written to Google Calendar, Microsoft 365 / Outlook.com, Apple iCloud (CalDAV) or the built-in calendar, with a confirmation, a calendar file and reminders.
- Bookings section on the dashboard: services, opening hours and special days, staff with their own hours and calendars, messages in your words, a Flow designer, several Flows per number with their own trigger words, an appointment list with cancel / mark completed / mark no-show, clients with memberships and credits, and reports.
- Inbox: every WhatsApp conversation in the dashboard, answered from there, with saved replies, templates when the 24 hour window is closed, and a contact panel with tags, membership and bookings.
- Public API: /v1/{number}/bookings (list, create, cancel, availability, settings), the booking.created / booking.cancelled / booking.rescheduled webhook events and matching MCP tools.
Agents, contacts, templates and a closer look at Meta fees
2026-11-02 in the next release - Hosted MCP server (POST https://api.app2email.com/mcp) so Claude, ChatGPT, Cursor and OpenClaw can send and read WhatsApp through your API key, plus a stdio package (npx @app2email/mcp).
- Conversation ownership and handoff API: an agent can hand a contact to a person ("human") or pause automation; the Auto Reply and A2A / OpenClaw agents respect it.
- Sandbox API keys (simulated sends with fake wamid.SANDBOX ids and real status webhooks), daily caps per key, and approval gates: sends above a threshold wait on the new Approvals page.
- Contacts page: tags, custom fields, CSV import and export, consent records (who agreed to marketing, when, how) and saved segments; broadcasts can go to a segment and can be scheduled.
- Templates page: create and submit templates (named or numbered placeholders, up to 10 buttons), see Meta's approval status, category changes, quality rating and rejection reasons.
- Links and QR codes page: click-to-chat links with a source tag, QR codes generated in your browser.
- Email bridge options: delivery receipts for failed replies, optional read receipt when the email is opened, quoted history.
- Meta fees panel on the dashboard home: free service messages used (1,000 a month), billable counts by category and an indicative estimate. Meta bills service replies beyond the allowance and in-window utility templates since 1 October 2026.
- Business-scoped user IDs: contacts who share a WhatsApp username instead of a phone number are now routed, logged and replied to correctly.
- Inbound media is stored by app2email when it arrives (Meta deletes it after 7 days).
- Template, category and quality webhooks from Meta are recorded and shown; a paused or rejected template sends you an email.
- API errors carry documentation_url, is_retriable and retry_after_seconds; API rate limits are enforced.
- Public status page, this changelog, a trust page with the sub-processor list and a draft DPA, email setup guide and agent integration guide.
- Members and roles (owner, admin, member, viewer) per number, with an audit log of dashboard changes.
- Compliance: automated-reply disclosure text, extra opt-out words, one CSV of consent and suppression records.
Public API v1
2026-10-26 - REST API at https://api.app2email.com/v1/{number}/... with scoped keys, IP allow-lists, expiry, rate-limit headers and a 30 day request log.
- Template sends to one or many numbers (per-recipient values), free-form replies inside the 24 hour window, scheduled sends, dry runs and background sends.
- Webhooks with signatures, retries, delivery history and redelivery; template, media, Do Not Call, opt-in and settings endpoints.
- OpenAPI 3.0 and Swagger 2.0 descriptions, Swagger UI, and a Markdown reference for AI agents (/docs-api.md, /llms.txt).
Reply Alerts
2026-10-20 - An email reply sent more than 24 hours after the contact's last message is held, and the contact gets a short WhatsApp notice with a "Show reply" button. Tapping it delivers the reply.
- Do Not Call list page with dates and sources; contacts who tap "Stop promotions" are added automatically.
OpenClaw channel and A2A agents
2026-03-01 - OpenClaw WebSocket channel (wss://ws.app2email.com) that works behind NAT with media inline.
- A2A (Agent-to-Agent) integration: incoming WhatsApp messages go to your own agent and its answer comes back to the contact.