API Introduction
About this API
The Global SMS Messaging API provides developers with a simple and efficient way to integrate SMS sending functionality into any application, website, or system. It supports sending text messages to mobile numbers in multiple countries and regions worldwide. Whether it's for critical user identity verification, real-time event notifications, or large-scale marketing campaigns, this API can provide reliable service with high delivery rates and low latency. By using pre-audited templates or sending custom content, you can easily establish a direct and instant communication channel with your global user base, enhancing user engagement and security.
Key Features
- Global Coverage: Supports sending SMS messages to mobile numbers worldwide, covering major countries and regions' telecom operators.
- Two Sending Modes: Supports both "template SMS" and "custom content SMS" modes. Template SMS is suitable for sending fixed-format verification codes and notifications, and can achieve higher sending speed and stability after review; custom content SMS provides greater flexibility.
- High Delivery Rate & Low Latency: Uses high-quality operator direct connection channels to ensure that SMS messages can be delivered to users' mobile phones within seconds and guarantees a very high delivery rate, which is crucial for time-sensitive verification codes and alerts.
- Two-Way Messaging: Supports two-way SMS functionality, not only sending messages but also receiving user replies, thus enabling the construction of interactive customer services, such as SMS voting, customer service inquiries, etc.
- Status Reports & Statistics: Provides detailed sending status reports, allowing you to know whether each SMS has been successfully delivered, and provides a statistical dashboard to help you analyze the effectiveness of SMS sending.
Use Cases
Scenario 1: Implement Secure and Reliable Two-Factor Authentication (2FA)
Situation: An online bank or e-commerce platform needs to add an extra layer of security verification when users log in or perform sensitive operations (such as large-value transfers). Implementation: When a user tries to log in, after entering their username and password, the backend system generates a random 6-digit verification code. Then, the system calls the Global SMS Messaging API, using a preset verification code template (e.g., "Your verification code is {#code#}, valid for 5 minutes."), to send this verification code to the user's pre-bound mobile number. The user must enter the received verification code to complete the login. This method greatly enhances account security and effectively prevents unauthorized access.
Scenario 2: Send Real-time Transaction and Logistics Status Notifications
Situation: An e-commerce platform wants to notify customers immediately when the order status changes. Implementation: The platform's order management system is integrated with this API. When the order status is updated to "shipped," the system will automatically call the API to send an SMS message containing the tracking number and a query link to the customer's mobile phone. When the package is signed for, the API is called again to send a "Your order has been delivered" notification. This proactive and timely communication method can significantly improve the customer's shopping experience and satisfaction.
Scenario 3: Execute a Precise Appointment Reminder Service
Situation: A clinic, restaurant, or service agency wants to reduce the waste of resources caused by customers forgetting their appointments. Implementation: The agency's appointment management system can set up a scheduled task. The day before the appointment (e.g., 24 hours in advance), the system will automatically call the SMS API to send a reminder SMS to the appointment customer's mobile phone, including the appointment time, location, and precautions, and can provide an option to reply "Y" to confirm or "N" to cancel. This not only effectively reduces the customer's no-show rate but also simplifies the appointment management process through two-way SMS functionality.
How it Works: Endpoints & Response
This API executes SMS sending tasks through a core sending endpoint.
Endpoint Example: https://hub.juheapi.com/international-sms/v1/send_mess
As the example shows, the API supports two request body structures:
- Template SMS: Requires providing
tpl_id
(template ID) andtpl_value
(variable values in the template). This method has a fast sending speed and the content is regulated by the operator, suitable for standardized notifications. - Custom SMS: Requires providing
mess_content
(SMS content). This method is more flexible but may require stricter content review.
Both methods require apikey
for authentication, as well as phone
(phone number) and area_code
(area code) to specify the recipient. The sign
field is usually your application or company signature. A successful API call will return a message ID, which you can use to query the subsequent sending status.