Integration typeEvent hooks + REST API
ZendSMS integration guide
Event hooks + REST APIConnect ClientExec notices to ZendSMS.
Send account, billing, service and support notifications from selected ClientExec events through a secure API bridge.
ClientExecBusiness event
ZendSMS202 QUEUEDYOURBRAND
A new support reply is available in your account.
✓ DeliveredSecurity patternServer-side only
Response202 Accepted + message_id
Common workflows
What you can send from ClientExec.
Keep hosting and service customers informed at important account moments.
Invoice due
Remind clients about an upcoming due date.
Payment status
Confirm successful or reviewed payments.
Service update
Notify customers about selected service lifecycle changes.
Ticket response
Send a concise alert when a support response is available.
Verified API pattern
From one business event to one trackable SMS.
This request uses the fields in the current ZendSMS Send SMS reference. Keep the API key in a secret store, attach a unique client_ref and save the message_id from the accepted response.
- 01
Define the workflow
Choose the event, recipient and message that should be sent.
- 02
Connect securely
Keep the API key on the server and make the request over HTTPS.
- 03
Map the template
Map the approved sender ID, recipient, message and client reference.
- 04
Test and launch
Check the result, segment count and delivery state before production.
POST /api/v1/send-sms202
Authorization: Bearer sk_your_api_key
{
"recipient": "8801700000000",
"sender_id": "YOURBRAND",
"message": "A new support reply is available in your account.",
"client_ref": "ce-ticket-2048"
}success: truestatus: QUEUEDmessage_id: UUID
Read the complete Send SMS reference Included in the workflow
Build a production-ready flow, not just a send button.
Event-driven SMS
Send only when a selected business event occurs.
Every core SMS type
Use OTP, Masking or Non-Masking SMS for the approved use case.
References you can track
Keep your own client reference and the returned message ID.
Bangla and Unicode
Send Bangla, English or Unicode content for the customer journey.
ClientExec FAQ
Answers to review before production.
A concise guide to security, SMS types, delivery reconciliation and testing.
Should the ClientExec integration call the API from a browser?
No. A secret API key must never be placed in browser code or public JavaScript. Send requests from a trusted server, backend function or protected connector.
Which SMS types can ClientExec send?
You can use OTP, Masking and Non-Masking SMS for an approved use case. Sender ID and template activation remain subject to KYC, documents and applicable operator or regulatory approval.
How do I reconcile delivery results?
Attach a unique client_ref to each request and store the message_id returned in the accepted response. Reconcile delivery status using the current API documentation.
What should be tested before launch?
Test event mapping, recipient format, Bangla/Unicode segments, duplicate prevention, error handling and delivery results. Complete consent and compliance review before production.
Related integrations
Explore another path for the same workflow.
Ready to connect?