Polymorfa vs OpenWA

Three reasons teams move from OpenWA

1. 01

   Built for serving many businesses

   Polymorfa's Customers API groups each business's numbers, pairing links and scoped tokens.² Each client pairs its own number on a hosted QuickLink page, and scoped API keys and the audit log cover your team.^8,9,10

   OpenWA: OpenWA supports many sessions for one operator, and its multi-tenancy design is not implemented.¹

2. 02

   The official route behind the same API

   Polymorfa's Graph API accepts Meta's request shape for linked-device and Cloud API numbers, so one integration covers both kinds of client. Cloud API onboarding through Embedded Signup is in beta.^3,8

   OpenWA: OpenWA's README sends regulated workloads to Meta's official Cloud API, which OpenWA does not connect to.¹¹

   curl -X POST "$OPENWA_URL/api/sessions/$SESSION_ID/messages/send-text" \
     -H "X-API-Key: $OPENWA_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"chatId":"15550001111@c.us","text":"Your order shipped."}'

   # Meta's request shape, for a linked-device or a Cloud API number
   curl -X POST "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": "15550001111",
       "type": "text",
       "text": { "body": "Your order shipped." }
     }'

3. 03

   No sessions on your servers, and calls from code

   Polymorfa runs the sessions, and you pay only for days a number is online.⁴ It places and answers calls in a browser, in server code or over a SIP trunk.^5,6

   OpenWA: OpenWA sessions run on your hardware at up to 500 MB each on its default engine. It handles incoming call events and rejection.¹¹