Polymorfa vs Meta Cloud API
From October 1, 2026, Meta charges for every reply, not only templates.
From October 1, 2026, Meta charges for every reply your business sends in the customer service window, and a Cloud API group holds at most 8 participants.1,2 Polymorfa keeps your Meta request code and adds linked-device numbers with no per-message fee, full groups and channels, and hosted onboarding and call audio.3,4,5,6
- Meta Cloud API
- Charged from Oct 1, 2026
- Polymorfa
- None on linked-device numbers
- Linked devices and the official Cloud API, behind one API.3
- 2 routes
- Per message. A number costs credits only for the days it is online.4
- $0
- To place and answer calls: in the browser, in server code with the raw audio, and on your PBX over SIP.6,7
- 3 ways
- In the hosted MCP server, for agents that run WhatsApp.8
- 195 tools
Three reasons teams move from Meta Cloud API
- 01
Keep your Meta code, add linked-device numbers
Polymorfa's Graph API accepts Meta's request shape for both Cloud API and linked-device numbers. Change the base URL and token; the body stays the same. An operation a route does not support returns a Meta-shaped capability error.3
Meta Cloud API: Meta's Cloud API serves official numbers only, with groups capped at 8 participants.2
meta.sh curl "https://graph.facebook.com/v23.0/$PHONE_NUMBER_ID/messages" \ -H "Authorization: Bearer $SYSTEM_USER_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "messaging_product": "whatsapp", "to": "15551234567", "type": "text", "text": { "body": "Your order shipped." } }'polymorfa.sh # Same body. Works for a Cloud API or a linked-device number. curl "https://api.polymorfa.com/graph/whatsapp/v26.0/$NUMBER_ID/messages" \ -H "Authorization: Bearer $POLYMORFA_PROJECT_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "messaging_product": "whatsapp", "to": "15551234567", "type": "text", "text": { "body": "Your order shipped." } }' - 02
An onboarding page you do not build
Polymorfa hosts the page. Send a QuickLink and your customer pairs a linked-device number or runs Embedded Signup for a Cloud API number, which is in beta. The Customers API groups numbers and links by customer.9,10
Meta Cloud API: Building direct, you pass app review and build the Embedded Signup flow in your own product.11
- 03
Calls without running a media stack
Polymorfa carries the audio. Answer in a browser, in server code that reads and writes PCM audio, or on your PBX through a SIP trunk. Cloud API calls are one-to-one audio; linked-device numbers also take video and group calls.6,7
Meta Cloud API: Meta's Calling API hands you signaling, and you carry the audio over WebRTC or SIP. Business-initiated calls are unavailable for business numbers in the US, Canada, Egypt, Vietnam and Nigeria.12
One credit pool. Only the days a number is online.
One credit balance pays for every number your team runs, and a number costs credits only for the UTC days it is online.4 The monthly bonus is part of the price: buy 100,000 credits in a month and you get 250,000.13
Bonus credits on the whole month's purchase, every month
- +10%
- from 10,000 credits
- +25%
- from 20,000 credits
- +75%
- from 50,000 credits
- +150%
- from 100,000 credits
What Polymorfa gives you that Meta Cloud API does not
| Feature | Polymorfa | Meta Cloud API |
|---|---|---|
| Linked-device numbers | Yes9 | Official route only |
| Group management | Linked device5 | Up to 8 participants2 |
| Channels | Linked device14 | Not documented |
| Idempotent sends | 24-hour keys15 | Not documented |
| MCP server for AI agents | Hosted, 195 tools8 | Not documented |
| Customer accounts for SaaS builders | Customers API10 | Tech Provider programme11 |
| Pricing model | Per online number-day16 | Per template message17 |
| Paid entry price | $0.25 per online day16 | No platform fee17 |
Move from Meta Cloud API in an afternoon
- 01
Create a project and a token
Sign up, create a project and generate a project token in the Console.
- 02
Connect your numbers
Send a QuickLink. Cloud API numbers use Embedded Signup, which is in beta and needs team access; linked-device numbers pair by QR or pairing code.9
- 03
Change the base URL
Replace https://graph.facebook.com/{version} with https://api.polymorfa.com/graph/whatsapp/v26.0 and keep the request bodies.3
Questions
What is a linked-device number?
A WhatsApp or WhatsApp Business app number connected as a companion device, the way WhatsApp Web connects. It manages groups and channels, beyond the Cloud API's 8-participant group limit.14,5,2
Are sends safe to retry?
Yes. Repeating a send with the same Idempotency-Key within 24 hours returns 409 idempotency_completed and does not send the message again.15
Leave the WhatsApp infrastructure to us.
Start freeUpdated . Other companies' pages checked on 24 September 2026.
- Meta Cloud API, Upcoming pricing updates for service and utility messages
- Meta Cloud API, Groups
- Polymorfa, Graph API
- Polymorfa, Usage and credits
- Polymorfa, Groups and chats
- Polymorfa, Calls
- Polymorfa, SIP trunks
- Polymorfa, MCP server
- Polymorfa, QuickLink
- Polymorfa, Customers
- Meta Cloud API, Embedded Signup
- Meta Cloud API, Calling
- Polymorfa, Billing
- Polymorfa, Channels
- Polymorfa, Messaging overview
- Polymorfa, Pricing
- Meta Cloud API, Pricing