Zernio WhatsApp API

One API for WhatsApp: messaging, calling, and AI agents

Messaging

API

Developer Tools

Visit WebsiteSee on Product Hunt

Strong launch. WhatsApp is one of those surfaces where the guardrail matters as much as the API call.

For agent workflows, I’d want a pre-send state check: window open or closed, template required, last inbound timestamp, and handoff owner. Are you planning that as a helper, or leaving it to builders?

Congrats on your launch. The thing I'd want to understand as someone building a product on top of this: if each of MY customers needs their own WhatsApp number connected, how painful does that get at scale? Can I wrap Embedded Signup into my own onboarding so a non-technical customer connects their WABA in a few taps, or does it always route through Meta's flow? Multi-tenant provisioning is usually where WhatsApp infra falls over. Great launch regardless.

Over 6 month in production with the WhatsApp SDK and it's running very smooth! Never had major issues and I love how much the team improves the product constantly, especially the WhatsApp connection. Heads up to the team for making it easy to connect with my clients and customers through their favorite channel 👍🏽
Keep building, keep moving
Leon 🐒

The channel line up is crazy @dasha_nazarova1

Does this mean through Zernio, there could also be 2-way AI-assisted Whatsapp conversation also possible?

And we all know how tricky it is to get things done through Meta, would Zernio assist in the process in case there are issues connecting and setting up Meta + WhatsApp?

Excited to explore this further during the weekend.

I think Zernio is so cool. We use it ourselves. I think they are just adding more and more massive advantages and just enable you to scale and build content and workflow distribution across multiple channels. Huge respect.

"Not can you send a message, but the whole thing" nails it, Miki. I build on the Meta WhatsApp Business API directly and sending was never the hard part. The pain is the BSP gatekeeping, number verification, template approval, and the 24h customer-care window that quietly kills any real automation. Routing calls to AI agents on the same number is the dream. Genuine question: how do you handle the 24h window and template approval? That's where every WhatsApp build actually breaks. Congrats on the launch.

WhatsApp API and dev experience are quite challenging, you solution seems very interesting! Do you have a list of all the use cases that you solution enables?

This looks awesome excited to try! Congrats on the launch @paletmiki

Guys, good stuff. How frequently can we fetch analytics from the LinkedIn API? Do you have access to ‘who viewed your profile?’

I really think Zernio is an absurdly efficient solution. Since I met them a few months ago when they were still Late, I fell in love with them and their products, and now I’m building solutions with them. This new integration with WhatsApp is definitely going to remove a lot of headaches for those of us who work with WhatsApp agents.

This is really cool! Having messaging, calls, and AI agents all through one WhatsApp API is a huge deal for developers. Quick question — does it support sending media files like images or PDFs in messages, or is it mainly text-based for now?

We haven't tested the WhatApp connection yet, But look forward to deploying it for our customers. I'm sure it's top notch as their other products which we have been testing for several months now. Keep up the good work, team! 🤘

the "zero markup on usage" line got me. dealing with Twilio's WhatsApp pricing on top of Meta's fees was killing margins on a project last year. having messaging, calls, and AI agent routing all in one integration without the markup games is exactly what i would've wanted. the MCP server being hosted is a nice touch for agent workflows too. curious how you're handling rate limits when multiple AI agents are hitting the same number concurrently?

The calling + AI agents combo in a single API is what makes this stand out - most WhatsApp integrations I've looked at just cover messaging. Been thinking about building something that handles voice callbacks automatically and the current options are painful. Question for the team: how does the rate limiting work when you're running outbound AI agent campaigns at scale? That's usually where these tools hit unexpected ceilings.

I have a question, how long does it take for approval, because i have a presentation August 12 and this will be useful for me

2 days - Thats all it took to be able to ship all of my backend on whatsapp. Real users testing. Zernio cut through all the Meta complexity so I could focus on the actual product especially for customers who never want to touch a website o and most almost never use a website or an app, either old people or just people who hate to learn new UIs, even if they are easy, Zernio allowed me to decrease my Time-to-Value a lot!
Keep it up guys!

Hey PH community!!

Carlos here - the Product Evangelist at Zernio, basically the guy whose job is to make noise about this thing across X, PH, and wherever you hang out.

Joined the crew a month ago and immediately got thrown into the fire. The team was already shipping at warp speed (small team, bootstrapped, zero bullshit), but my mission is crystal clear: get this API in front of every solopreneur, AI agent builder, and tool maker who's tired of wrestling with 15 different platform APIs just to ship social features.

I've been out here posting, threading, and hunting conversations with you guys — the real ones building in public.

Watching this tiny squad (5 people max) ship features that save months of eng time has been wild. No VC theater, just raw execution.

So if you're a builder embedding social into your product, cooking autonomous agents that actually act on X/IG/TikTok, or just tired of the integration tax... hit me up.

Now we are on PH to make Zernio BIG. 🚀