A WhatsApp API you can actually build on
Scoped keys, predictable JSON envelopes, HMAC signed webhooks — plus a Model Context Protocol (MCP) server in the works, so your AI coding agents can drive WhatsApp too.
curl -X POST https://app.vyaparping.com/api/v1/messages \
-H "Authorization: Bearer vp_live_xxx" \
-d '{ "to": "+919958662072", "type": "text", "text": "Hi 👋" }'Drive WhatsApp directly from Claude & Cursor
We're building an official MCP server so you can connect VyaparPing to your IDE and local LLM agents. Read incoming threads, triage customer tickets, and trigger broadcasts under the exact same permission scopes as any API key.
Preview the planned setup & JSON spec →{
"mcpServers": {
"vyaparping": { "command": "npx", "args": ["-y", "@vyaparping/mcp-server"] }
}
}Predictable REST API
Clean endpoints for messages, contacts, conversations, and template statuses with cursor-based pagination.
HMAC-SHA256 Webhooks
Cryptographically signed payloads for inbound messages, delivery status changes, and new conversations.
Granular Scoped API Keys
Enforce least privilege: separate keys for read-only analytics, message sending, and contact syncing.
Further reading
Background guides on the setup, pricing and mechanics behind this page.