Your integration surface, a real REST API plus webhooks to build on.
WBIZ gives developers a clean REST API and signed outbound webhooks, so you build the integration you actually need. No markup over WhatsApp rates, no rate-limit gating beyond fair use, granular per-key scopes, reveal-once secrets, and an embedded API playground.
POST /v1/messages/text and /v1/messages/template. Reveal-once secrets. HMAC-signed outbound webhooks.
Public REST v1
Two well-defined send endpoints: text and template.
POST /v1/messages/text sends free-form text inside the WhatsApp 24-hour window. POST /v1/messages/template 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.
- POST /v1/messages/text for free-form text within the 24h window
- POST /v1/messages/template for approved templates any time
- Per-key scopes such as contacts:read and webhooks:manage
- Reveal-once secrets, so leaked keys are easy to rotate
curl -X POST https://api.wbiz.in/v1/messages \
-H "Authorization: Bearer wbiz_live_xxx" \
-H "Content-Type: application/json" \
-d '{
"to": "+919876543210",
"type": "template",
"template": {
"name": "order_dispatched_v3",
"language": "en_IN",
"components": [
{ "type": "body", "parameters": [
{ "type": "text", "text": "Priya" },
{ "type": "text", "text": "#4421" }
]}
]
}
}'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.
- 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
Webhook events
Live- message.receivednowyour-app.com/hooks
- message.delivered1syour-app.com/hooks
- message.read3syour-app.com/hooks
- conversation.assigned12syour-app.com/hooks
- campaign.completed4myour-app.com/hooks
Embedded API playground
Try the API in the dashboard, with one-click temporary keys.
An embedded API playground lives at /docs/playground/ and at /app/api-playground/ inside the portal. Newly-issued playground keys flow straight into the playground, so you can try the API in seconds without touching production credentials. The same playground is available before login on the marketing site.
- Playground at /docs/playground/ and /app/api-playground/
- One-click temporary playground keys
- Freshly-issued keys flow straight into the playground
- The same playground component on the marketing site
curl -X POST https://api.wbiz.in/v1/messages \
-H "Authorization: Bearer wbiz_live_xxx" \
-H "Content-Type: application/json" \
-d '{
"to": "+919876543210",
"type": "template",
"template": {
"name": "order_dispatched_v3",
"language": "en_IN",
"components": [
{ "type": "body", "parameters": [
{ "type": "text", "text": "Priya" },
{ "type": "text", "text": "#4421" }
]}
]
}
}'By the numbers
What teams ship on WBIZ.
0
Public send endpoints: text and template
0
Reveal-once secret per key
0
HMAC-signed webhook delivery
0
Markup over WhatsApp rates
Build on WBIZ. Build any integration via REST and webhooks.
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.
REST and playground
Two send endpoints, with an embedded playground at /docs/playground/ and /app/api-playground/.
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.
India-first hosting
Hosted in India by default. Encryption in transit, and secrets stored encrypted at rest.
Use any tool
Bring your existing dev workflow.
A standard REST API plus signed webhooks slots into whatever stack you run. There are no prebuilt connectors, so you bring your own glue.
REST
POST /v1/messages/text and /template
Outbound webhooks
HMAC-signed, retried, dead-lettered
Embedded playground
/docs/playground/ and /app/api-playground/
Scoped keys
Granular per-resource permissions
Per-event filtering
Subscribe to only what you need
India-hosted
Encryption in transit and at rest
FAQ
API, answered.
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.
You can call the Cloud API directly. WBIZ wraps it with stable send endpoints, scoped API keys, signed outbound webhooks with retries and a dead-letter queue, an embedded playground, and a version-upgrade story so your code keeps working.
Each workspace can hold multiple API 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.
Yes. Every webhook 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.
In India by default: built in India and hosted in India. Encryption in transit, and secrets stored encrypted at rest.