Meta-compatible requests - Polymorfa

The Messaging API includes a Meta Cloud API-compatible interface. Repoint an existing integration from https://graph.facebook.com to https://api.polymorfa.com, keep the vNN.0 path segment and Meta request shape, and authenticate with a Polymorfa project credential.

curl -X POST "https://api.polymorfa.com/v21.0/$PHONE_NUMBER_ID/messages" \
  -H "Authorization: Bearer $TITAN_PROJECT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "messaging_product": "whatsapp",
    "to": "15551234567",
    "type": "text",
    "text": { "body": "Hello from Polymorfa" }
  }'

Endpoint families

Family	Current paths
Messages and media	`/{version}/{phoneNumberId}/messages`, `/{version}/{phoneNumberId}/media`, `/{version}/{mediaId}`, `/{version}/{mediaId}/download`
Numbers and profiles	`/{version}/{wabaId}/phone_numbers`, `/{version}/{phoneNumberId}/whatsapp_business_profile`
Templates	`/{version}/{wabaId}/message_templates`
Calling and QR	`/{version}/{phoneNumberId}/calls`, `/{version}/{phoneNumberId}/message_qrdls`
Automation and safety	`/{version}/{phoneNumberId}/conversational_automation`, `/{version}/{phoneNumberId}/block_users`
Commerce and marketing	`/{version}/{phoneNumberId}/whatsapp_commerce_settings`, `/{version}/{phoneNumberId}/marketing_messages`
Registration	`/{version}/{phoneNumberId}/register`, `/{version}/{phoneNumberId}/deregister`, `/{version}/{phoneNumberId}/request_code`, `/{version}/{phoneNumberId}/verify_code`
Uploads and diagnostics	`/{version}/{appId}/uploads`, `/{version}/{uploadId}`, `/{version}/debug_token`
WABA apps and Flows	`/{version}/{wabaId}/subscribed_apps`, `/{version}/{wabaId}/flows`

The generated Meta-compatible endpoints group under Messaging API documents the exact query parameters, request bodies, and Meta-shaped response and error envelopes.

Backends and errors

The same facade can resolve a linked-device or Cloud API session. A capability that the selected backend cannot perform returns a Meta-compatible error instead of a Polymorfa-native envelope. Tenant and project ownership are checked before any media, upload, template, or session effect.

Version behavior

The first segment must match vNN.0; the API defaults to v21.0. Meta-compatible versioning is separate from the date-pinned Titan-Version header used by native requests.