Twilio goes global with cloud telephony

News James Stirling Oct 18, 2012

Cloud-based communications extended to 40 countries and six continents.

Cloud telephony start-up Twilio has announced that its communications services are now on six continents and 40 countries.

The announcement made at the company’s Twilio conference in San Francisco means that app developers can use the cloud-based service in more countries than ever before. Among the new countries are Australia, Brazil, Japan, and South Africa.

"In 2012, we set out to make Twilio a single API with global reach," said Jeff Lawson, chief executive and co-founder of Twilio. "Now that we are on six continents, developers and their companies can reach their customers around the globe. As we continue our expansion efforts, we can't wait to see what developers everywhere around the globe will build."

Developers can now deploy services using the cloud telephony service to more countries without having to rewrite code or deal with new carriers. Developers are now able to buy local phone numbers in forty countries, all using the same Twilio API. This eliminates the burden of customers having to individually manage country by country carrier relationships.

Lisa Weitekamp, associate product manager at Twilio said that the company had taken a deliberate approach to expansion.

"We have established strong relationships with providers around the world to provide the highest quality possible,” she said. “Before launching in each country, we do extensive investigation on local regulations and restrictions, and we make sure that we have a process that makes it easy for our customers to build incredible apps and services, regardless of their country."

The company also a number of new APIs to allow developers to build more stable cloud applications as well as retrieve data more easily and show usage information.

With new Test Credentials for the Twilio API, developers can test their code against the Twilio API without placing calls, sending SMS messages, or spending a penny. Developers can use the same code to talk to the same Twilio API in their tests as they do in their production environments, but by using Test Credentials they'll no longer worry that a runaway test might result in a significant cost.

The Usage API gives developers a REST endpoint to query any type of Twilio usage with a single API call. The API supports slicing and dicing usage over any date-range and by any time-interval.

Finally, the Usage Triggers API allows developers to create triggers that webhook to their application when it crosses usage thresholds. Usage Triggers can fire, based on any type of usage from a specific call-type to the total price of all usage.