Rest easy with our API, knowing its infrastructure was built
for reliability, security, and scalability.
You need a reliable SMS service API to make sure your application runs smoothly. We spent as much time making our API run reliably as we did making our great features.
Because we manage multiple paths to wireless carriers, your messages are delivered reliably by our SMS service, even if one of our network partners (data centers, Internet providers, cloud service providers, etc.) is experiencing a problem. Just as we provide failover testing for hardware components like servers and disks, we do so even for our aggregators.
To support our email service, we host several hundred email servers and IP’s, ensuring that your emails are delivered in large quantities with minimum delivery rejection and junk labeling.
Users can also receive delivery reports for messages, providing them with up-to-date information about which contacts are invalid.
As a premier SMS API provider, we provision your account with a shared short code. This enables you to scale from dozens of messages per second, up to hundreds of messages per second, given the proper use case and plan.
Our service is deployed in active-active setups to ensure maximum uptime. If one server in a cluster was to go down due to unexpected issues, another server would automatically take its place, providing continuity with no impact to the end user.
We also utilize two data centers in geographically distinct areas to ensure continuity of service even in the event of a natural disaster or power outage.
Our automated monitoring systems analyze network traffic conditions 24/7 so our engineers, network providers and carriers can be notified immediately when a delay or downtime is detected in transmission of text messages. Most issues are resolved without any impact to our end users.
Users must authenticate themselves before accessing our service. Web users do this via a username and password, while API users do this with a username and a randomly generated API key. All login attempts are logged in our system and audited for suspicious activity.
You can also bolster security by requiring a one-time code that’s either emailed or texted to you when someone tries to login from a foreign IP address.
All data in our messaging service API is compartmentalized, so users can access only their own data. You will soon be able to limit access to users within your own account, by issuing users their own API keys with their own sets of permissions and data.
Within our data center, server access is limited to the intranet, and a secure VPN is required to tunnel in from outside the intranet. Access logs are reviewed regularly, and intrusion prevention systems are kept up to date in order to prevent security breaches.
Also in place is a DOS prevention system that automatically blocks clients from making excessive requests to the server. DOS attack incidents are logged and reported to the incident management team, which analyzes them and takes the necessary steps to prevent further incidents.
All data in transmission can be encrypted with TLS if the user chooses to use HTTPS.
Behind the firewall is an up-to-date antivirus system that actively scans for security vulnerabilities and viruses. If a virus is detected, the system will quarantine the infected files. The system then alerts the security administrator to any detected problems, and the administrator immediately works to resolve the issue.
Our servers are located in secured data centers that require several forms of authentication and identification for access. The data center is monitored 24/7 with CCTV systems and detailed access logs to minimize the risk of damage or theft. In addition, our servers are housed in locked cages to avoid unauthorized physical access.