Skip to content
WhatIsUp.dev

WhatIsUp.dev

A lightweight, developer-first WhatsApp Gateway. Spin up a WhatsApp channel via REST, send messages, receive events as signed webhooks. No Twilio markup, no Meta business-verification queue, no SDK that hides the wire format.

Why this exists

Most WhatsApp gateways are either resellers of the official Cloud API — slow, expensive per message, gated on Meta business verification — or black-box SaaS wrappers that break whenever WhatsApp changes anything.

WhatIsUp.dev sits in between: a clean HTTP API on the front, a maintained WhatsApp protocol layer on the back, with the operational pieces a developer SaaS needs — typed contracts, signed webhooks with retries, bearer-token API keys, a channel lifecycle you can poll or subscribe to, and an SDK story that's just fetch. You bring your own WhatsApp number, you scan a QR once, you ship.

What you get

  • REST API — channels, messages, webhook endpoints, API keys. JSON in, JSON out.
  • Signed webhooks — X-WhatIsUp-Signature: t=<ts>,v1=<hmac>, verified the same way Stripe does.
  • Realtime SSE stream — /v1/events for QR codes and channel state changes without polling.
  • Public Zod contracts — every request, response, and webhook payload is published as a typed schema, so you can generate clients in any language without us having to ship one.

What you don't get (yet)

  • Official Cloud API parity — this is a Web-protocol implementation. The platform can change it, and occasionally does; we track upstream.
  • Multi-region writes — single primary database for v1. Fine for the workloads we target.
  • Object storage for inbound media — attachments are cached in memory and proxied via signed URLs. See Concepts → Webhooks.

This project is for developer-tier use. Don't use it for compliance-bound workflows (healthcare, regulated finance, anything that requires the official Cloud API's business-account guarantees). It's a wrapper around an unofficial protocol.

Where to next