Check out our Launch week free trial and the Polymorfa Builders Program! 15 Pro numbers + add-ons for 30 days.

Ends in ––d : ––h : ––m : ––s
Polymorfa

Command Palette

Search for a command to run...

Platform

One API for both WhatsApp backends.

Meta Cloud and Linked Devices behind one payload shape: full coverage of messages, media, templates, calls, and webhooks, routed by where the number lives.

Start buildingRead docs

One API. Both WhatsApp backends.

Meta Cloud and Linked Devices behind a single payload shape. Send once and Polymorfa routes to wherever the number lives, with full 1:1 coverage of messages, media, templates, calls, and webhooks.

Meta Cloud

Official Cloud API

Linked Devices

WhatsApp Web protocol

Polymorfa Cloud

One payload shape · routes by where the number lives

RESTMCPSDKsn8n

Hybrid Link

Pair Meta COEX mode with the Linked Devices API on the same number. Conversations start on the free path so you never pay Meta to initiate them. And with Meta moving non-template messages to per-message pricing, every conversation Hybrid Link keeps off the meter is billing you simply never see.

You start the conversationLinked Devices
Customer replies in 24h windowMeta Cloud
Meta per-message fees avoided−$15.44
Reliability

Boringly online.

Sessions reconnect, refresh, and migrate between backends without dropping state. Multi-region AWS, zero-downtime deploys, and a session engine you get to forget about, which is the point.

99.9%Uptime targetMulti-region AWS with automatic failover between zones.
<3sReconnectDropped sessions re-establish with exponential backoff and resume cursors.
187msp95 sendQueue to WhatsApp receipt, measured across production sends.
0Downtime deploysDate-pinned versions ship behind the API without a blip.
API availabilitystatus.polymorfa.com
90 days ago1 partial degradation · 22 mintoday
Session engine

The layer you never think about.

Every number is a long-lived session that something has to keep alive, ordered, and consistent. That something is us.

Reconnects itself

Network drops, phone restarts, and WhatsApp hiccups are absorbed with backoff and resume, no webhook gaps.

Migrates without a deploy

Move a number between Linked Devices and Meta Cloud; the payload shape and your code stay identical.

Keeps state consistent

Ordered delivery, resumable cursors, and exactly-once webhooks even across reconnects and migrations.

Stack

Five SDKs, one contract.

Every SDK is generated from the live OpenAPI contract and hand-tuned so it feels handcrafted. Database sync adapters consume your webhooks on the platform you already run.

TypeScriptPythonGoPHPRust
SupabaseConvexFirebaseCloudflareVercelAWSAzureGCPDigitalOceanNetlify

22+ surfaces, one OpenAPI contract.

Pin a date. Upgrade when you choose.

Your integration pins a version date and keeps working. Breaking changes only ever ship behind a new date, and sunset headers appear in responses months before anything is removed.

POST /v1/messages
Polymorfa-Version: 2026-06-01
2026-06-01currentCalls GA · media download moves into the SDKs
2025-12-01supportedWebhook payloads gain session_health
2025-06-01sunsets 2027-01Legacy media endpoints, header warns on every response
Console

Watch it all happen in the console.

Everything the API does is visible: live logs, session health, webhook replays, key scopes. If you can do it over REST, you can watch it happen here.

console.polymorfa.dev/logs
TimeEventStatusms
14:02:11message.received20012
14:02:11webhook.delivered2008
14:02:37message.sent20241
14:03:02session.refresh20096

Live from the console, every row replayable.

Deep dive

Two backends, one contract.

WhatsApp exists twice: Meta's hosted Cloud API, and the Linked Devices protocol that powers WhatsApp Web. Different strengths, different prices, different limits.

Polymorfa's job is making that difference boring. One payload shape, one webhook contract, one console; numbers move between backends without a deploy.

120+
API actions
30
webhook events
5
SDK languages
How it works

How a message travels.

Every send takes the same three hops, whichever backend the number lives on.

1
You call POST /v1/messagesSame body for text, media, templates, or interactive messages.
2
Polymorfa normalizes and queuesValidated, rate-shaped by BanSafe, signed, and stamped with your version date.
3
Routed to the right backendDelivered over Meta Cloud or Linked Devices; receipts stream back as webhooks.
By the numbers

The surface area.

Coverage is the product: if WhatsApp can do it, the API exposes it.

API actions120+
Webhook events30
SDK languages5
Uptime target99.9%
Versioningdate-pinned

Ship a WhatsApp integration this afternoon.

Free on the sandbox. No credit card. The projects you start here migrate straight into production.

Start buildingBook a demo