Waappa API Guide

WhatsApp Webhook API

Waappa webhooks help applications react to WhatsApp activity in real time. Your app can receive inbound messages, delivery events, session updates, and automation triggers, then route them to AI agents, CRMs, support desks, databases, or monitoring workflows.

What webhooks unlock

Webhooks turn WhatsApp from a manual inbox into an event source. Your backend can listen for customer replies, update records, trigger AI responses, and alert teams without polling.

  • Inbound messages
  • Delivery status events
  • Session status changes
  • Support ticket creation
  • CRM updates
  • AI-agent triggers

Good webhook design

Production webhook handling should verify events, process idempotently, retry safely, and log failures. For AI workflows, store enough context to avoid repeated or confused replies.

Automation examples

A webhook can qualify a lead, detect payment screenshots, route urgent messages to a group, generate an AI draft, or notify a sales owner when a prospect replies.

  • AI support assistants that answer FAQs, collect context, and escalate to humans.
  • Sales follow-up agents that qualify leads and remind teams when prospects reply.
  • Order, payment, delivery, and appointment alerts from internal systems.
  • n8n automations that connect WhatsApp to Google Sheets, CRMs, help desks, and databases.
  • Monitoring alerts for servers, payment failures, job queues, forms, and operational incidents.
  • Group-based internal workflows for field teams, agencies, communities, and operations teams.

Pricing

Waappa uses session-based pricing for predictable WhatsApp automation costs.

Most popular

Starter

For testing, solo builders, and one WhatsApp account.

₹699/mo

+ GST

  • 1 connected WhatsApp account
  • Linked-device QR connection
  • REST API and webhooks
  • Text, media, document, contact, and location messages
  • No Waappa per-message fee
  • 3-day free trial

Growth

Best for small teams running support, sales, and automation flows.

₹1,999/mo

+ GST

  • 3 connected WhatsApp sessions
  • Approx ₹666 per session
  • SDKs, n8n nodes, MCP, and webhooks
  • Group and channel workflow support
  • Higher automation capacity
  • Best value for growing teams

Business

For teams that need more numbers, routing, and monitoring.

₹2,999/mo

+ GST

  • 5 connected WhatsApp sessions
  • Approx ₹600 per session
  • Business automation workflows
  • Sales, support, and monitoring use cases
  • Priority guidance for setup
  • Lower per-session cost

Partner

For agencies, SaaS builders, and resellers managing many clients.

₹1,999 platform/mo

+ GST

  • ₹1,999 platform fee
  • ₹599 per active session/month
  • Approx ₹20 per active session/day
  • Pay as you grow
  • Useful for client-by-client billing
  • Partner onboarding support

Official API vs Waappa

The official WhatsApp API and Waappa solve different problems. Use this comparison to choose the right fit.

Area
Waappa linked-device API
Official WhatsApp API
Connection model
Connect an existing WhatsApp account by QR/session linking.
Connect through Meta's WhatsApp Business Platform and approved business setup.
Best for
Developers, AI agents, n8n workflows, internal monitoring, groups, sales follow-ups, and flexible automations.
Verified business messaging, large brand campaigns, template-based notifications, and compliance-heavy use cases.
Existing WhatsApp use
Can use WhatsApp as-is with the connected account experience.
Usually requires official business setup, phone number onboarding, and approved messaging flows.
Groups
Useful for group automation, internal alerts, and operations workflows.
Official Cloud API is generally focused on business-to-user messaging, not broad group automation.
Message cost
No Waappa per-message fee. Pricing is based on connected sessions.
Platform/provider costs plus Meta message/template fees may apply.
Templates
More flexible for normal conversational workflows.
Template approval is central for business-initiated messages.
Risk profile
Bulk or spam-like usage can cause account blocks, reports, or disconnects.
More formal compliance model, but still subject to Meta policy and quality controls.
Developer flexibility
REST API, webhooks, SDKs, n8n, MCP, AI agent workflows, media, contacts, locations, groups, and monitoring flows.
Strong official APIs for approved business messaging, templates, webhooks, and enterprise messaging.

Bulk Messaging Safety

Linked-device WhatsApp automation is powerful, but aggressive bulk messaging can cause reports, blocks, or disconnections.

  • Use opt-in contacts and avoid cold spam.
  • Add delays between messages instead of blasting instantly.
  • Personalize messages and avoid sending identical text to large lists.
  • Respect replies, blocks, opt-outs, and customer preferences.
  • Use groups for relevant internal or community workflows, not unsolicited promotion.
  • Warm up new numbers slowly and monitor delivery, reports, and disconnections.

FAQ

Do webhooks work for AI assistants?

Yes. Webhooks provide the incoming message events that an AI assistant needs to classify, answer, summarize, or escalate a WhatsApp conversation.

Should I retry failed webhook processing?

Yes. Use idempotency and retries so temporary failures do not lose important WhatsApp events.

Can bulk messaging get blocked?

Yes. Any WhatsApp account can face blocks, reports, rate limits, or disconnection if it sends spam, cold bulk messages, repetitive content, or messages without consent. Waappa should be used with delays, opt-ins, human-like pacing, and real customer context.