Launching today
Unlimited Messaging
Send WhatsApp and email from one API, no monthly cap.
1 follower
Send WhatsApp and email from one API, no monthly cap.
1 follower
UnlimitedMessaging centralises WhatsApp and email in one place. Developers get a REST API, real-time webhooks (delivered, read, replied) and Python/Node.js SDKs. One API call sends via WhatsApp, email, or both at once. The built-in CRM handles the rest: segment your audience, view conversation threads per contact, track delivery and read status, and reply directly from the interface. No per-message fee. No vendor lock-in.
Hello Product Hunt!
We built UnlimitedMessaging after hitting the same wall repeatedly: per-message pricing that kills margins at scale, separate tools for WhatsApp vs email, and a nightmare of environment variables, provider credentials and webhook configs spread across three services just to send a single message.
Most messaging setups we've seen look the same: one .env for the WhatsApp provider, another for the email provider, a third service for webhooks, and a custom CRM on top to tie it all together. Every new project starts with the same two hours of plumbing before writing a single line of actual product code.
UM collapses that into one setup. Connect your WhatsApp number and email mailbox once. From there, one API key covers everything: sending on both channels, receiving webhooks for delivered, read and reply events, and querying your contact and message history. No extra credentials to rotate, no provider-specific quirks to abstract away.
The built-in CRM handles the non-developer side too: segment your audience, view full conversation threads per contact, track who read what and when, and reply without leaving the app.
We would love feedback on two things:
- How many .env variables and external services does your current messaging stack require? Would a single API key actually simplify your setup?
- Does having the CRM and the API in the same product change how you'd approach a new project?