Polymorfa vs BotConversa

Three reasons teams move from BotConversa

1. 01

   An API that is the product, not a tab in the settings

   Polymorfa is only an API. Every inbound message and status change arrives on your webhook, signed with HMAC-SHA256 and delivered in up to eight attempts over 24 hours, set per webhook, and delivery and attempt records are readable through the API.³ Sends accept an Idempotency-Key, so a retried request does not message the customer twice.⁹

   BotConversa: BotConversa's API key lives under Configurações, next to the Zapier key, and the API works on contacts and flows rather than on the conversation.¹⁰

   curl 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":"+5511999990000"},"content":{"text":"Seu pedido saiu para entrega."}}'
   
   # A repeat within 24 hours returns 409 idempotency_completed.
   # Replies arrive on your webhook, signed in X-Webhook-Signature.

2. 02

   A contract you can pin, and keys you can scope

   Polymorfa requests carry a Polymorfa-Version contract date, and the reference is published as OpenAPI 3.1.¹¹ Project keys take only the scopes you select, and development prerelease SDK documentation covers authentication and requests.^12,13

   BotConversa: BotConversa has one full-access key per company and a Swagger page that follows whatever is live.^10,2

3. 03

   Built for many clients, on either route

   The Polymorfa Customers API groups numbers by the business they belong to, and QuickLink lets each client connect its own number. The route is chosen per number, and the Graph API takes Meta's request shape for both. Cloud API onboarding is in beta.^14,15,4

   BotConversa: On BotConversa, the plan decides whether a number connects by QR or by the official API, and each number is its own company with its own key and its own R$ 199 monthly Starter plan.^1,16,10