High-Quality SMS with a custom sender, real-time delivery reports, and instant sending.
Integrate via API a global professional SMS service, ideal for two-factor authentication (2FA), notifications and alerts, appointment reminders, and critical communications, ensuring security, speed, and complete tracking of every message.
The sender of the message must be an alphanumeric alias (between 3 and 11 characters) and cannot be purely numeric. If null or empty, "Openapi" will be used as the default sender.
The sender must be an alphanumeric alias (between 3 and 11 characters) and cannot be purely numeric. If null or empty, "Openapi" will be used as the default sender.
In what format should the recipient's number be provided?
The recipient's phone number must be provided in the standard international E.164 format, with the following structure:
- + (plus sign)
- Country code
- Subscriber number, including area/prefix
The number must be entered without spaces, dashes, or parentheses and can have a maximum length of 15 digits.
Example (Italy):
+39 333 1234567 → +393331234567
Any number sent in a format other than E.164 will be considered invalid and classified as an incorrect recipient.
Yes, the API allows sending long messages, i.e., messages longer than 160 characters for GSM-7 encoding or longer than 70 characters for UCS-2 encoding.
Yes, it is possible to check the message length and estimate the number of SMS segments that will be used before actual sending.
During the request, you can simulate sending by setting the dryRun parameter to true. This way, the system returns a forecast of the number of SMS segments and the related cost, without actually sending the message.
Additionally, the failOnMultipleMessages parameter can be used to prevent unwanted sends: if the text exceeds the length of a single SMS, the request is automatically blocked and returns an error, preventing concatenated messages and additional costs.
Yes, verification OTP messages can also be sent via the dedicated endpoint POST /OTP.
With the SMS API, messages can be sent to over 250 countries.
The full list of supported countries and corresponding rates is available on the pricing page: https://openapi.com/prices/sms
There are six possible statuses for SMS messages:
- NEW
- PENDING
- UNDELIVERABLE
- DELIVERED
- EXPIRED
- REJECTED
The maximum delivery attempt period is 48 hours. If a message is not delivered within this interval, its status will become EXPIRED.
You can check in real-time via the endpoint GET /messages/{id} to see if a message has been sent, is being delivered, has been delivered, or encountered an error.
In the Usage section at the API level, you can monitor both free and paid requests. Data is available in graphical format (monthly and yearly periods) as well as a textual summary:
Yes, subscriptions are currently available for Italy and Spain, starting at €0.036 for Italy and €0.027 for Spain.
The cost of sending an SMS varies depending on several factors, including message length, destination country, and the recipient’s mobile operator.
The full and updated pricing list is available at: https://openapi.com/prices/sms
Exceptions for Italy and Spain
Unlike other countries, Italy and Spain apply a flat rate, independent of the recipient's operator.
Italy
- From €0.049 per SMS with subscription billing
- €0.036 per SMS with prepaid/recharge billing
Spain
- From €0.027 per SMS with subscription billing
- From €0.039 per SMS with prepaid/recharge billing