Polymorfa vs Rasayel

Three reasons teams move from Rasayel

1. 01

   Webhooks you can build a business on

   Polymorfa signs every delivery with HMAC-SHA256, in its own format with X-Webhook-Signature or in Meta's with X-Hub-Signature-256. It makes up to eight delivery attempts over 24 hours, set per webhook, and delivery and attempt records are readable and retryable through the API.²

   Rasayel: Rasayel's webhook guide describes an HTTP POST to your endpoint and does not document how to verify that it came from Rasayel.⁹

   import { createHmac, timingSafeEqual } from "node:crypto";
   
   // meta format: X-Hub-Signature-256 is "sha256=" + HMAC-SHA256 of the raw body
   function verify(rawBody: string, header: string, secret: string) {
     const expected = Buffer.from("sha256=" + createHmac("sha256", secret).update(rawBody).digest("hex"));
     const received = Buffer.from(header);
     return expected.length === received.length && timingSafeEqual(expected, received);
   }

2. 02

   Meta's request shape, on both routes

   Polymorfa's Graph API accepts Meta's request shape for linked-device and Cloud API numbers, so code written for Meta keeps working, and the number you address decides the route. Cloud API onboarding through Embedded Signup is in beta.^4,10

   Rasayel: Rasayel runs on the official API only, through its own GraphQL mutations.^1,11

3. 03

   An API that is the product, not a line on a seat plan

   Polymorfa publishes an OpenAPI 3.1 reference pinned by a Polymorfa-Version contract date, development prerelease SDK documentation, and an MCP server with 195 tools.^12,13,8 You pay per connected number for each day it is online, with unlimited team members.^5,3

   Rasayel: On Rasayel, API access arrives with the inbox seats you buy.¹