What the WatEase developer API covers
Scoped API keys
Generate keys from the dashboard, scoped per operation with default-deny — a reporting key reads stats and can do nothing else. Revoke instantly.
Campaign endpoints
Create broadcast campaigns, upload audiences, and trigger sends over REST — the same policy-safe engine the dashboard uses, driven from your code.
Delivery & read statistics
Per-campaign delivery and read stats plus an account-level summary endpoint, ready for your BI dashboards and data warehouse.
Webhooks
Events flow outward to your systems as they happen, so your CRM and analytics stay current without polling.
Policy safety inherited
API sends ride the same engine that enforces opt-ins, templates, and the 24-hour window — your integration cannot fire an out-of-policy message.
Native integrations
Shopify two-way sync, Tally GST-clean export, and Razorpay/PhonePe/Paytm gateways ship built-in — the API covers what they don't.
Key features: developer REST API, scoped API keys with per-operation access control, instant key revocation, campaign creation and audience upload endpoints, programmatic sends, per-campaign delivery and read statistics, account-level stats summary, webhooks, policy-safe send engine (opt-ins, approved templates, 24-hour window), custom integrations and bespoke customization (Enterprise plan), and native Shopify, Tally, and payment-gateway integrations.
How the integration works
- Generate a scoped key. In the dashboard under Settings → API keys, create a key and grant it exactly the operations it needs — everything not granted is denied by default.
- Call the REST endpoints. Authenticate each HTTPS request with an
X-API-Keyheader (orAuthorization: Bearer). Create a campaign, upload its audience, trigger the send. - Read the results. Pull per-campaign delivery and read statistics or the summary endpoint into your reporting; consume webhooks to keep your CRM and warehouse current as events happen.
Because the API drives the same engine as the dashboard, sends inherit every policy guarantee: opt-outs halt delivery, templates are Meta-approved, and the 24-hour service window is enforced — an integration bug cannot damage your number's quality rating.
Custom integrations and bespoke customization for enterprise
When the integration should be built for you rather than by you, the Enterprise plan includes it in the contract: WatEase engineers connect your CRM, ERP, data warehouse, ticketing, or in-house software, and build bespoke workflows, reports, and features around your exact processes. API rate limits and webhook capacity are raised to your negotiated volume, and an integration engineer joins your named-CSM team. The full enterprise picture — governance, SSO/SAML, audit logs, data residency, SLA — is on the WhatsApp Business Platform for Enterprise page.
The API works best with the rest of the stack
Programmatic campaigns pair with the platform surfaces business teams run themselves: the WhatsApp automation page covers no-code journeys, the broadcast software page covers segmented campaign sends, and the Business API provider page covers getting your number onto the official API in the first place. Plans and Meta conversation charges are on the pricing page.
Frequently asked questions
What is WhatsApp API integration?
WhatsApp API integration means connecting WhatsApp messaging to the software your business already runs — CRM, ERP, e-commerce backend, data warehouse — so campaigns, messages, and delivery events flow programmatically instead of through a dashboard. Two layers are involved: Meta's WhatsApp Business API carries the messages, and a platform API like WatEase's developer REST API gives your engineers endpoints for campaign creation, audience upload, sends, and delivery/read statistics, plus webhooks for events — without building template management, opt-in state, and quality-rating handling from scratch.
Does WatEase have a developer API?
Yes. WatEase ships a developer REST API: you generate scoped API keys from the dashboard (Settings → API keys), authenticate with an X-API-Key header or Authorization: Bearer token, and call endpoints to create broadcast campaigns, upload audiences, trigger sends, and read delivery and read statistics per campaign or as a summary. Webhooks deliver events outward. Keys are scoped per operation and revocable instantly, and the Enterprise plan raises rate limits and webhook capacity to your volume.
What is the difference between the WhatsApp Business API and the WatEase developer API?
The WhatsApp Business API is Meta's raw messaging pipe — it moves messages but ships no campaign engine, audience management, template workflow, or analytics; you build those. The WatEase developer API sits one layer up: the platform already runs templates, opt-ins, quality-rating protection, journeys, and the commerce loop, and the API exposes programmatic control over it — create a campaign, upload the audience, send, read the stats. Most teams integrating WhatsApp want the second shape; raw CPaaS (Gupshup, Twilio) is the right shape when engineering wants to own the whole stack.
How do I secure a WhatsApp API integration?
Use scoped credentials, not master keys. WatEase API keys are scoped per operation — a key can be limited to exactly the endpoints it needs (for example campaigns:read for a reporting job, or send permissions for a campaign runner) and everything else is denied by default. Keys are revocable instantly from the dashboard, access is enabled per workspace, and every request authenticates over HTTPS with an X-API-Key header or bearer token. Grant each vendor or internal service its own key with the minimum scopes, and rotate on personnel changes.
Can WatEase integrate WhatsApp with our CRM or ERP?
Yes, two ways. Self-serve: your engineers use the developer REST API and webhooks to wire WhatsApp campaigns and events into any system that speaks HTTP. Done-for-you: the Enterprise plan includes custom integrations as a contract deliverable — WatEase engineers connect your CRM, ERP, data warehouse, ticketing, or in-house software, and build bespoke workflows and reports around your processes. Native integrations for Shopify (two-way sync), Tally (GST-clean voucher export), and Razorpay/PhonePe/Paytm gateways ship out of the box.
Which WatEase plans include API access?
API access with webhooks is listed from the Pro plan (₹3,999/month) up, and the Enterprise plan raises API rate limits and webhook capacity to negotiated volume and adds custom integrations and bespoke customization as contract deliverables. API access is enabled for your workspace as part of plan setup. Meta's per-conversation charges apply as usual and pass through at 0% markup on every plan.