Whats91 API Overview

Whats91 is a developer layer over Meta WhatsApp Cloud API. Customers generate a Whats91 public API token, call Whats91 v2 endpoints, and Whats91 handles sender resolution, billing and blacklist guards, media handling, report logging, reconnect queues, and Meta API submission.

Base URL

https://graph.whats91.com/api/v2

Build public integrations around the canonical base path above. The backend also mounts a smaller /v2 surface for send/chat/messages compatibility, but /api/v2 is the documented path for this portal because it includes message and template management routes.

Public v2 APIs

What Whats91 Handles

• Resolves the customer's connected WhatsApp sender from the token, senderId, or phoneNumberId route.
• Applies billing, account-state, blacklist, and sender reconnect guards before submitting to Meta.
• Accepts JSON and multipart requests for send/chat/template APIs where supported.
• Stores send attempts and webhook updates so dashboard reports can show accepted, sent, delivered, read, failed, and queued states.
• Uses Meta Graph API behind the scenes for message sends, template create/list/status, media handling, and webhook subscriptions.

Quick Example

curl -X POST "https://graph.whats91.com/api/v2/chat" \
  -H "Authorization: Bearer w91_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "senderId": "919999999999",
    "to": "918888888888",
    "type": "text",
    "text": "Hello from Whats91"
  }'

Dashboard Context

Internal dashboard APIs such as API token management, templates, webhooks, reports, and live logger routes are session-authenticated workflow surfaces. Public integrations should call the bearer-token v2 APIs documented here, not dashboard session APIs.