Access
Scoped API credentials
Separate OTP and custom-message clients, rotate secrets, and restrict sender access.
Integration path
Add WhatsApp messaging without rebuilding your backend.
Connect OTP and customer-message workflows through scoped API keys, predictable REST requests, signed webhooks, and delivery diagnostics your team can operate.
RESTSimple HTTP requests
SERVERSecrets stay private
WEBHOOKSDelivery events
Server-side request
Send OTP
typescript
await fetch(`${baseUrl}/api/otp/send`, {
method: 'POST',
headers: {
'content-type': 'application/json',
'x-api-key': process.env.WHATSAPP_API_KEY,
},
body: JSON.stringify({ receiver_number, app_name: 'My Store' }),
});A production path your team can follow
Move from credential creation to delivery tracking in four explicit steps.
- 01
Create an API key
Choose OTP or message access and assign only the senders this integration needs.
- 02
Store it server-side
Keep credentials in environment variables and call HookMessage from your backend.
- 03
Send a test request
Validate phone formatting, payload fields, idempotency, and the queued response.
- 04
Track delivery
Use message status and signed webhooks to reconcile delivered or failed requests.
Integration architecture
The important controls are already separated.
Your application owns the customer event. HookMessage owns sender execution, plan enforcement, queue state, and delivery visibility.
Requests
Backend-first API calls
Use REST endpoints from server actions, jobs, controllers, or application services.
Events
Signed delivery webhooks
Receive lifecycle updates without exposing private credentials in the browser.
Operations
Limits and diagnostics
See plan limits, sender state, API errors, and delivery history in one dashboard.
Use the stack you already run
The API contract stays the same across frameworks and background workers.
JavaScript / TypeScript
Fetch, Node.js, Express, Fastify, and server-side framework routes.
Next.js / React
Route handlers or server actions keep the API key outside the client bundle.
PHP / Laravel
Use the HTTP client from controllers, jobs, listeners, or service classes.
Python
Call the REST API from Django, Flask, FastAPI, workers, or scheduled tasks.
Working example
JavaScript fetch
Send an OTP from a backend action or API route.
typescript
await fetch(`${baseUrl}/api/otp/send`, {
method: 'POST',
headers: {
'content-type': 'application/json',
'x-api-key': process.env.WHATSAPP_API_KEY,
},
body: JSON.stringify({ receiver_number, app_name: 'My Store' }),
});Working example
PHP
Trigger a customer confirmation from a PHP app.
php
$response = Http::withHeaders([
'x-api-key' => env('WHATSAPP_API_KEY'),
])->post($baseUrl.'/api/messages/send', [
'receiver_number' => $phone,
'message' => 'Your order is confirmed',
]);Optional implementation help
Launch with an integration review.
Share your stack, expected message volume, sender plan, and first workflow. We can help review the implementation path before customer traffic goes live.
300–700 DHone-time setup range
Review checklist
- Review the customer event that should trigger a message
- Choose OTP, transactional messaging, or both
- Create and scope the correct API credentials
- Connect a sender and validate production readiness
- Implement retries, idempotency, and webhook verification
- Test failures, limits, and delivery-state handling before launch
First workflow
Test the complete request before production.
Create a sandbox workspace, issue a scoped key, and validate success and failure responses from your backend.