Cover SMS, calls, WhatsApp and email with precise event names.
WEBHOOK V2 · EVERY MOBILE EVENT, DELIVERED TO YOUR SOFTWARE
Turn every event from your connected mobile into an instant action.
SMSMobileAPI Webhook V2 sends structured HTTPS events to your applications when an SMS is submitted, sent, failed or received, when a mobile call is missed, incoming or outgoing, and when supported WhatsApp or email activity occurs. Configure everything visually from your dashboard—no polling loop required.
Read the API documentationChoose the events each destination receives. Test, pause, monitor and rotate its signing secret from one workspace.
SMSCALLWAEMAIL
signed JSON
SMSMobileAPIWEBHOOK V2Durable event queue
LIVE
HTTPS POST
CRMSUPPORTAUTOMATIONANALYTICS
Send different event groups to different HTTPS destinations.
Verify every request using its HMAC-SHA256 signature and timestamp.
Temporary destination failures are retried without blocking other accounts.
HOW WEBHOOK V2 WORKS
From a real mobile event to your application in three clear steps.
Your connected mobile and SMSMobileAPI services produce operational events. Webhook V2 places each eligible event into a durable delivery queue and sends a signed JSON payload to the HTTPS URL you selected.
- 1
An event happens
A message is submitted, a mobile sends or receives an SMS, a call changes state, or supported WhatsApp and email activity is recorded.
- 2
Webhook V2 routes it
SMSMobileAPI creates one stable event ID and queues a delivery only for destinations subscribed to that event type.
- 3
Your software reacts
Your public HTTPS endpoint verifies the signature, stores the event ID and starts your CRM, support, alerting or automation workflow.
15 PRECISE EVENT TYPES
Subscribe only to the mobile events your workflow needs.
One destination can receive everything, or you can separate production systems, analytics and operational alerts. Every event has a precise name so your application can handle it predictably.
SMS
5sms.api.submittedSMS submitted through API
An API request created an SMS sending job. Useful for acknowledging that the request entered the platform.
sms.sentSMS sent
The connected mobile confirmed the SMS sending operation.
sms.failedSMS failed
The connected mobile returned an SMS sending error.
sms.receivedSMS received
A connected mobile synchronized an incoming SMS.
sms.mobile.sentSMS sent from mobile
An SMS was sent manually from the connected mobile.
Calls
3call.missedMissed call
A missed call was synchronized from a connected mobile.
call.incomingIncoming call
An incoming call was synchronized from a connected mobile.
call.outgoingOutgoing call
An outgoing call was synchronized from a connected mobile.
whatsapp.submittedWhatsApp submitted
A WhatsApp sending job was created.
whatsapp.sentWhatsApp sent
The connected WhatsApp environment confirmed the message was sent.
whatsapp.failedWhatsApp failed
The WhatsApp sending operation failed.
whatsapp.receivedWhatsApp received
A WhatsApp message was retrieved after the account requested synchronization.
whatsapp.voice.transcribedVoice message transcribed
An eligible retrieved WhatsApp voice message was converted into usable text.
email.sentEmail sent
An email sending request was created by SMSMobileAPI.
email.receivedEmail received
A connected mailbox received an email.
CONFIGURE EVERYTHING VISUALLY
Professional webhook management without editing configuration files.
Open Webhook V2 in the SMSMobileAPI dashboard, add a destination name and public HTTPS URL, select the events, then save. The dashboard gives you the controls required for day-to-day operation and troubleshooting.
Multiple destinations
Create dedicated destinations for your CRM, monitoring, analytics or customer applications.
Event filters
Select exactly which SMS, call, WhatsApp and email events each URL receives.
Test delivery
Send a controlled test event before relying on the destination in production.
Pause and reactivate
Stop one destination instantly without deleting its configuration.
Secret rotation
Generate a new signing secret when your security process requires it.
Delivery activity
Review queued, delivered, retrying and failed deliveries with attempt and HTTP status information.
Webhook V23 active
CRM production
https://crm.example.com/hooks/mobileACTIVEsms.receivedcall.missedwhatsapp.received
Operations alerts
https://ops.example.com/eventsACTIVEsms.failedwhatsapp.failed
RELIABILITY BY DESIGN
Built for reliable, independent delivery.
Webhook delivery is asynchronous. Your mobile workflow does not wait for a third-party URL to respond, and one failing destination does not block another customer or destination.
Durable queue
Eligible events are stored before delivery so temporary receiver downtime does not erase the event.
At-least-once delivery
A delivery may be retried. Store the event ID and process it only once in your own application.
Progressive retries
Temporary failures are retried with increasing delays, up to the platform retry limit.
Failure isolation
A slow or unavailable endpoint cannot stop delivery to unrelated destinations.
Automatic protection
A destination with sustained failures can be paused to protect the queue and your infrastructure.
Operational visibility
The dashboard and webmaster monitoring expose queue health, results and recent delivery errors.
SIGNED AND VERIFIABLE
Verify the request before trusting the event.
Each delivery includes a timestamp, delivery identifier, event type, stable idempotency key and HMAC-SHA256 signature. Keep the signing secret on your server, calculate the signature from the raw request body and reject invalid or stale requests.
X-SMSMobileAPI-EventThe event type, such as sms.received.X-SMSMobileAPI-DeliveryThe unique delivery identifier for this destination.X-SMSMobileAPI-TimestampUnix timestamp used during signature verification.X-SMSMobileAPI-SignatureHMAC-SHA256 signature to compare securely.Idempotency-KeyStable event UUID used to prevent duplicate processing.CONSISTENT EVENT ENVELOPE
One consistent JSON envelope for every channel.
The envelope remains predictable across SMS, calls, WhatsApp and email. The data object contains the fields relevant to the event type, while the top-level identifiers let you route and deduplicate every delivery.
id— stable event identifiertype— exact event typeoccurred_at— when the activity happeneddata— channel-specific information
{
"id": "whv2_01J...",
"type": "sms.received",
"api_version": "2026-09-22",
"created_at": "2026-09-22T12:00:00Z",
"occurred_at": "2026-09-22T11:59:58Z",
"data": {
"guid": "...",
"from": "+32...",
"message": "Can you call me back?"
}
}FROM EVENT TO BUSINESS OUTCOME
Make mobile communication trigger the next business action.
CRM conversations
Add a received SMS or WhatsApp message to the correct contact and alert the assigned owner.
Missed-call recovery
Create a callback task, send a follow-up SMS or notify an on-call team after a missed call.
Customer support
Open or update a support ticket when a customer replies from their mobile.
E-commerce operations
Update order communication workflows after a mobile message is sent, confirmed or fails.
Monitoring and alerts
Send delivery failures or unusual call activity to your observability and incident tools.
AI and data workflows
Feed authorized events into classification, reporting or assistance workflows without repeatedly polling the API.
STOP POLLING FOR CHANGES
Polling asks repeatedly. Webhooks notify your software when something changes.
Polling consumes requests even when nothing happened and adds delay between checks. Webhook V2 pushes the relevant event to your endpoint, making automation faster, simpler and easier to scale.
Any new event?Repeated requests · additional delay
EVENT
Notify me when it happens.Relevant event · immediate workflowWEBHOOK V2 FAQ
Questions before connecting your endpoint.
Do I need to build a polling loop?＋
No. Webhook V2 sends subscribed events to your public HTTPS endpoint. You can still use the APIs when you need to query history or details.
Can I configure several webhook URLs?＋
Yes. You can create multiple destinations and choose a different set of events for each one, within the account limits shown in the dashboard.
How do I know an SMS was really sent?＋
Use sms.api.submitted to know the job was created and sms.sent for the confirmation reported by the connected mobile. Treat them as two different operational stages.
Can a webhook be delivered more than once?＋
Yes. Webhook V2 uses at-least-once delivery. Save the stable event ID or Idempotency-Key and ignore a delivery you already processed.
What must my endpoint return?＋
Return an HTTP 2xx response after safely accepting the event. Processing can continue asynchronously inside your application.
Are received WhatsApp events collected continuously?＋
No. WhatsApp received-message retrieval follows its own consent-based synchronization process. The whatsapp.received event is available after an eligible message has been retrieved.
YOUR MOBILE EVENTS. YOUR SOFTWARE. YOUR ACTIONS.
Connect your software to the activity of your real mobile now.
Create your account or sign in, open Webhook V2, add a public HTTPS destination and choose the events that matter to your workflow. Send a test event, verify its signature and activate your integration.
