v1.10.0
Added
- Business-scoped user IDs — customers who hide their phone number (WhatsApp usernames) can now be replied to: pass messages[].from_user_id from your webhook as to on POST /v1/messages/send, send-template, read and typing, and it is routed to the Cloud API's recipient parameter. recipient is accepted as an alias for the ID. One-tap, zero-tap and copy-code authentication templates still need a phone number (422 meta_rejected with the reason)
- Webhooks already carried the IDs — messages[].from_user_id and contacts[].user_id on every WhatsApp event, statuses[].recipient_user_id on status events, contacts[].profile.username when set — and the 24-hour window is now tracked under the ID as well as the number, so a reply to either passes the window check
- Disconnecting a client — DELETE /v1/clients/{client_ref} (scope clients:write), and a Disconnect action on the client's page in the dashboard. Immediate and final: sends and webhooks for the number stop, its delivery logs are removed, Intelli stops receiving events for its WhatsApp Business Account; the number can be connected again later under any reference. Templates stay in the client's account
Improved
- Bigger bundles at the same price — Growth now includes 15,000 messages a month (was 10,000) and Scale 65,000 (was 50,000). Overage is unchanged at $0.004 and $0.003 per message. Existing subscriptions move to the new bundle automatically at their next billing sync, with no proration
- Reconnecting a client — a signup session created with a client_ref you already use now reconnects that client (same number, fresh connection) instead of returning 409, and the client's page in the dashboard has a one-click Reconnect. The session carries reconnect: true and the completion reconnected: true; a different number going through the popup is refused with 409 client_number_mismatch and leaves the client untouched
- A connection that Meta issued without template permission (whatsapp_business_management) is now flagged at signup — on the hosted page and under client.warnings on POST /v1/clients/signup — instead of at the first template. Template errors client_token_invalid, template_permission_missing, whatsapp_permissions_missing, waba_mismatch and waba_inaccessible all resolve by reconnecting the client