Tropo Web API - Drive our Voice and SMS cloud remotely via HTTP
The Tropo Web API is a web-service API that lets you build communications applications that run on your servers and drive the Tropo cloud using JSON over HTTP. It uses the same request-response model many web developers are already comfortable using, communicating with applications running on your own server, feeding requests and processing responses back and forth as needed.
The WebAPI is particularly useful in situations where, for example, you need to use a custom library (or libraries), or need access to a SQL database. The WebAPI allows for the deep backend integration you may need, but does, however, require you have your own infrastructure, your own hosting, and your own servers already in place.
Quickstarts are fast, easy to follow examples that exemplify the ease of use and simplicity behind Tropo's functionality. They cover everything from answering incoming calls, sending text messages, mixing voice and text in an application, recording calls, creating conference calls and much, much more.
There are three additional libraries available for use, though they will not be reflected in the examples:
...and just for some extra potential help, while these libraries were not created by us, they may still be useful:
- Groovy JSON Package
- PHP JSON Manual
- Python JSON Library
- Ruby JSON Library
If the example cannot be handled using JSON alone (such as an example that requires if/then/else logic, which JSON cannot do, or needs to parse data out of JSON like the response to an ask), then only library examples will be included. Many of the library examples will also include a framework; we use Sinatra with Ruby, express.js for Node.js, Limonade with PHP, itty with Python. You are not restricted to the frameworks we use - it's completely up to you. Expect these examples to potentially differ widely from each other; what works with one may not work for another.
Tutorials take a more in depth look at utilizing some of the core and ancillary functionality of Tropo, through the demonstration of examples built to showcase more complexity. Each of these will utilize one of the libraries, as pure JSON is significantly limited in scope.
The nitty gritty gospel behind every Tropo example, broken down and explained piece by piece. Want to know if a parameter takes an Integer or a Float? Need to know every possible option available on record? Want to know the default timeout value for ask? This is the place to go. All the examples here will be pure JSON.