Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Building a WhatsApp API with 0 markup on Meta pricing

Details

External ID
47514705
Source
HN
Company
—
Product
Building a WhatsApp API with 0 markup on Meta pricing
Website domain
zernio.com
Launched
March 25, 2026
Cohort
—
Upvotes
7
Upvotes percentile
0.4108241082410824
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Hey HN, I'm Pau. We've been building Zernio for the past 9 months and we just crossed $1M in ARR (bootstrapped).Zernio is a unified API for social platforms. One API for Instagram, TikTok, YouTube, LinkedIn, X, and 9 others. Today we're adding WhatsApp.We've spent 3 weeks just getting a test message to send. Meta requires a developer app, a WhatsApp Business Account inside Business Manager, business verification (2-14 days), phone number OTP, webhook configuration with a two-step subscription, and token management for tokens that die every 60 days. Miss one step and messages vanish with no error.So we built it so our users don't have to deal with any of that. Connect via Embedded Signup, get an API key, start sending. 37 endpoints covering messaging, broadcasts, templates, contacts, and phone number provisioning.The pricing model: zero markup on Meta's per-message rates. Most BSPs add 20%+ on top. We charge per account, not per usage.Docs: https://docs.zernio.com/platforms/whatsappHappy to answer questions about WhatsApp API integration or how we got to $1M ARR bootstrapped :)

Enrichment

Theme
payments, billing, and wallet infrastructure
Vertical
Retail & commerce
Function
Vertical SaaS
Audience
B2B
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
whatsapp api with no markup pricing
Manually corrected
False

Could you build this?

Partial Wrapping WhatsApp Business API and social endpoints into unified JSON schemas is vibe-codeable, but meeting enterprise SLAs, Meta Business Solution Provider verification, and webhook scale requires heavy operations.

What it would actually take: The architecture requires an API gateway (e.g., Go/Node), distributed worker queues (Temporal or RabbitMQ/Redis), and webhook processors designed to handle massive throughput and idempotency. The hard parts are navigating Meta's stringent Cloud API / WhatsApp BSP certification, webhook rate limiting, template registration workflows, and maintaining 99.99% uptime across brittle upstream social network APIs. It demands significant integration infrastructure engineering and formal partner compliance management.

Discussion

6 comments analyzed.

Competitors

Other products that read as similar to this one — 95 launches clear the similarity bar, closest 8 shown.

Attention rank: #45 of 96 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 140 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a vertical saas tool for Insurance yet.