Polymorfa vs Bird

Three reasons teams move from Bird

1. 01

   Keep the app, add the API

   Polymorfa pairs the number as a linked device with a QuickLink, by QR code or pairing code. The owner keeps chatting from the phone while your code sends, receives, creates groups and posts to channels.^2,8,9

   Bird: Bird connects a number through Meta's signup only after its WhatsApp app account is deleted.¹

2. 02

   Meta's request shape for every number

   Polymorfa's Graph API takes Meta's JSON body for linked-device and Cloud API numbers alike, so code written against Meta's documentation works as it is.^3,10

   Bird: Bird's send endpoint uses its own shape: flat to and from fields, and templates addressed by a Bird slug.¹¹

   curl -X POST https://us1.platform.bird.com/v1/whatsapp/messages \
     -H "Authorization: Bearer $BIRD_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "to": "+15551234567",
       "from": "+15550001111",
       "text": { "body": "Your order shipped." }
     }'

   # Meta's body. Works for a Cloud API or a linked-device 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": "15551234567",
       "type": "text",
       "text": { "body": "Your order shipped." }
     }'

3. 03

   WhatsApp calls from your code

   Polymorfa places and answers WhatsApp calls 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.^5,6

   Bird: Bird's API reference has no WhatsApp call operation.¹²