Connect
Pair a sender and keep its health, ownership, and workspace access visible.
Loading your content
Loading your contentMessaging infrastructure
Connect senders, issue scoped API keys, deliver OTP and customer messages, then track every status and callback from one controlled workspace.
Validated API request
Scoped key and sender policy
Controlled processing and retry
Observable delivery outcome
Every layer stays visible from setup to delivery.
Pair a sender and keep its health, ownership, and workspace access visible.
Issue purpose-scoped API keys for OTP or custom-message workflows.
Validate and queue every request before handing it to an allowed sender.
Follow delivery status, failure details, usage, and signed webhook events.
Start with the API and add operational surfaces as the workflow grows.
Purpose-built endpoints for verification and transactional customer communication.
Connect, assign, monitor, and constrain WhatsApp senders by workspace.
Create, rotate, revoke, and scope credentials without exposing dashboard sessions.
Standardize message content and securely deliver supported images and documents.
Receive lifecycle events with endpoint controls and delivery history.
Keep customer conversations, assignments, and operational follow-up in one place.
Trigger controlled workflows from customer and message lifecycle events.
Inspect delivery health, quota consumption, and account activity without guesswork.
Developer first
curl -X POST https://api.hookmessage.com/api/messages/send \
-H "x-api-key: YOUR_API_KEY" \
-H "content-type: application/json" \
-d '{
"sender_id": "YOUR_SENDER_ID",
"receiver_number": "+212612345678",
"message": "Your order is ready.",
"source_system": "checkout"
}'For operators
Give the team the visibility required to operate customer messaging while credentials and authorization remain server-side.
Operational snapshot
Assigned only
No blocked jobs
Signed events
Workspace history
Security is enforced in the workflow, not presented as decoration.
Customer data, API clients, sender assignments, and usage stay workspace-scoped.
OTP and custom-message permissions are enforced by the API, not only by the interface.
Each client can use only active senders explicitly assigned to its workspace.
Rotate and revoke credentials while retaining diagnostics and audit visibility.
Verify message events before your backend trusts or processes them.
Review status, failures, and sensitive activity from one controlled surface.
The same controlled infrastructure supports multiple product journeys.
Verify signups, logins, and orders with a simple API call and message log.
Confirm checkout, payment, and fulfillment updates for opted-in customers.
Send a first WhatsApp response after a form submission or landing page lead.
Notify sales or support when new customer events need human follow-up.
WhatsApp OTP
Send verification codes from your website or app with sender and usage controls.
Order Confirmation
Trigger customer order, payment, and delivery confirmations automatically.
Lead Follow-up
Reply after form submissions with a controlled customer confirmation flow.
Sales Notifications
Route opted-in lead alerts and internal updates to the right team members.
Start with the product
Test the API in a sandbox, connect a sender when ready, and keep delivery visible as usage grows.