// the take
A PHP client for Meta's WhatsApp Cloud API covering nearly every message type Meta exposes (text, media, templates, interactive lists/buttons, catalog, reactions) plus webhook parsing for inbound messages and status updates. Aimed at PHP shops building WhatsApp-based notifications, support bots, or commerce flows without rolling their own HTTP layer against Meta's API.
Message type coverage is genuinely wide — templates with component parameters, multi-product/catalog messages, CTA URL messages, and typing indicators are all here, not just the usual text/image demo. The webhook side uses a proper factory pattern (NotificationFactory/StatusNotificationFactory) that maps Meta's payload shapes to typed classes instead of leaving you to parse raw JSON. It has both unit and integration test suites (the latter hitting real WhatsApp API credentials), a CHANGELOG, and an UPGRADE.md for the v1→v2 break, which is more documentation discipline than most API wrapper repos bother with.
No retry or backoff handling for rate limits or transient Meta API errors — a ResponseException bubbles straight up and you're on your own for backoff logic in anything production-grade. Webhook verification only covers the initial GET challenge; there's no HMAC (X-Hub-Signature-256) check on incoming POST payloads shown anywhere, so an app built straight from the README is trusting unauthenticated webhook bodies unless the developer adds signature verification themselves. It's effectively a single-maintainer project (Netflie) wrapping a third-party API Meta can and does change without notice — the v1→v2 breaking migration already happened once, and template creation/update payloads are raw associative arrays with no schema validation, so a malformed template definition fails at Meta's servers rather than locally.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →