REST and playground
Two send endpoints, with an embedded playground in the docs and the portal.
Read the docs
REST API and outbound webhooks
Your integration surface: a real REST API plus webhooks
WBIZ gives developers a clean REST API and signed outbound webhooks, so you build the integration you actually need. No markup over WhatsApp rates, granular per-key scopes, reveal-once secrets, and an embedded API playground you can try before login.
38% reply rate
12,480
Delivered
9,134
Read
₹4.2L
Attributed
2
Send endpoints: text and template
1
Reveal-once secret per key
1
HMAC-signed webhook delivery
0
Markup over WhatsApp rates
Public REST v1
Two well-defined send endpoints: text and template
One endpoint sends free-form text inside the WhatsApp 24-hour window. The other sends an approved template at any time. Both accept the contact phone in E.164, return a typed response, and respect the window rules, so you never accidentally send a marketing template into a closed window.
- Send free-form text within the 24-hour window.
- Send approved templates at any time.
- Per-key scopes such as contacts:read and webhooks:manage.
- Reveal-once secrets, so leaked keys are easy to rotate.
Delivered · read
Auto-reply sent
Hi, is the Diwali offer still on?
Yes! 20% off till Sunday. Want the catalogue?
Please send it
Sent. Reply BUY to order in chat.
Outbound webhooks done right
HMAC-signed POSTs, retried and dead-lettered
Subscribe a URL to per-event filters. Every webhook is HMAC-signed, retried on failure with backoff, and falls into a dead-letter queue you can replay. Test-fire any event from the dashboard and see the full delivery history per subscription. Rotate the signing secret without dropping events.
- An HMAC-SHA256 signature on every payload.
- Per-event filtering, so you subscribe to only what you need.
- Retries with backoff and a dead-letter queue.
- Test-fire from the dashboard, with delivery history per subscription.
Flow live
Welcome
Ask intent
Route
Sales
Send catalogue
Support
Open ticket
Embedded API playground
Try the API in the dashboard, with one-click temporary keys
An embedded playground lives in the docs and inside the portal. Newly-issued playground keys flow straight in, so you can try the API in seconds without touching production credentials. The same playground is available before login on the marketing site.
- A playground in the docs and inside the portal.
- One-click temporary playground keys.
- Freshly-issued keys flow straight into the playground.
- The same playground component on the marketing site.
5,000 queued
5,000
Audience
80/min
Throttle
Opted-in
Only
For platform teams
Build on WBIZ, build any integration
There are no prebuilt connectors today, and that is on purpose. The WBIZ REST API and outbound webhooks are your integration surface, so you build the connector your business actually needs. WBIZ also carries the WhatsApp API version-upgrade work, so your codebase does not have to.
Signed webhooks
HMAC-SHA256, retries with backoff, a dead-letter queue, per-event filtering and secret rotation.
Scoped API keys
Granular per-key scopes such as contacts:read and webhooks:manage, with reveal-once secrets.
FAQ
API, answered
Are there prebuilt third-party connectors?
No. WBIZ ships a public REST API and HMAC-signed outbound webhooks, and that is your integration surface. Build whatever connector your business needs against a real, documented API, with no prebuilt vendor lock-in.
Why use WBIZ instead of the WhatsApp Cloud API directly?
You can call the Cloud API directly. WBIZ wraps it with stable send endpoints, scoped API keys, signed webhooks with retries and a dead-letter queue, an embedded playground, and a version-upgrade story so your code keeps working.
How are API keys managed?
Each workspace can hold multiple keys with granular per-resource scopes such as contacts:read and webhooks:manage. Secrets are reveal-once at creation, and you rotate by issuing a new key and revoking the old one. Playground keys are one-click and temporary.
Are webhooks signed?
Yes. Every payload is signed with HMAC-SHA256 using your shared secret. Retries fire on failure with backoff, and failures land in a dead-letter queue you can replay from the dashboard. Per-event filtering and secret rotation are built in.
Where does the API run?
In India by default: built in India and hosted in India. Encryption in transit, and secrets stored encrypted at rest.
Explore more
Pairs well with
Automations
Call your backend from a webhook action mid-run.
Learn moreContacts
Create, read and update contacts over REST.
Learn moreTemplates
Send approved templates straight from the API.
Learn moreWire WhatsApp into your stack in an afternoon
Read the docs, grab a playground key, and ship against a real, documented API.