Polymorfa vs whatsapp-web.js

Three reasons teams move from whatsapp-web.js

1. 01

   No browser to run for each number

   Polymorfa runs the sessions and stores their keys. Your code sends over HTTP.¹

   whatsapp-web.js: whatsapp-web.js runs WhatsApp Web in a Puppeteer-controlled browser, and sending video requires Google Chrome.⁹ You run that browser, keep it patched and store the session with an authentication strategy.¹⁰

   const { Client, LocalAuth } = require('whatsapp-web.js')
   
   const client = new Client({ authStrategy: new LocalAuth() })
   client.on('ready', async () => {
     await client.sendMessage('15550001111@c.us', 'Your order shipped.')
   })
   client.initialize()

   curl -X POST https://api.polymorfa.com/messaging/support/messages/send \
     -H "Authorization: Bearer $POLYMORFA_API_KEY" \
     -H "Idempotency-Key: order-1042-shipped" \
     -H "Content-Type: application/json" \
     -d '{"conversation":{"phoneNumber":"+15550001111"},"content":{"text":"Your order shipped."}}'

2. 02

   Webhooks and retries built in

   Polymorfa signs every delivery with HMAC-SHA256 and makes up to eight delivery attempts over 24 hours, set per webhook.² A send with an Idempotency-Key that repeats within 24 hours returns 409 and does not send again.¹¹

   whatsapp-web.js: whatsapp-web.js delivers events inside your process. Forwarding them to other services, signing them and retrying failures is yours to build.⁹

3. 03

   Calls from code and over SIP

   Polymorfa places and answers calls in a browser, in server code that reads and writes the audio, or on your PBX through a SIP trunk. Linked-device numbers also take video and group calls.^3,7

   whatsapp-web.js: whatsapp-web.js represents an incoming call as a Call object whose one method is reject().¹²