Before we get into the nuts & bolts of TringMe APIs, lets consider few use cases to understand typical API uses:
Use-case 1: Suppose you have a web portal where you would like to have a very easy-to-use way for your customers to call you. Customers can specify his or her number in a form on your website and then a call should be automatically initiated between both of you. Depending on your business-model, either you or your customer can bear the call-charges. To achieve this, you would typically expect following from the API:
Here is how TringMe API completely meets above requirements
Use-case 2:Taking the above use-case further, lets say that you wanted the ability for individual departments (sales, support, technical, finance) within your company to manage the calls separately - i.e. they should be able to interact with customers via calls and you want to get complete call records per department. To achieve this, you would typically require the following from the solution provider API:
Complete user-management capabilities are provided by TringMe APIs which make all the above fully possible. Infact user is a fundamental concept in TringMe API as explained below.
In TringMe APIs, everything revolves around a user. For e.g. When you make a call, the call will be billed to a user. The call-record for that call will go into that user's call-records. That call will bear the caller-id of that user.
TringMe APIs allow you to create as many users as you would like and initiate an action on that user account. For e.g. depositing credits in that user account, making call or sending sms etc. For e.g. as you can see in the use-case 2 above, you can create a user for every department.
A user context in TringMe API is identified by a cookie. As you would've guessed by now, the cookie is used in most TringMe APIs to take action on behalf of that user.
Cookie is an integral part of most TringMe APIs and identifies the user on whose behalf the action is being taken. For e.g. to place a call, you would pass a cookie and the billing of that call will be applied to the user to whom that cookie belongs.
Whenever a user logs-in, a cookie is assigned to that user. Read the login API to learn more.
You don't need to download any source-code or libraries to invoke TringMe APIs. TringMe API calls are made over the internet by sending the standardized HTTP GET or POST requests to TringMe's API server. For example, to get the TringMe user id, invoke a URL like this:
Ofcourse, we don't expect you to build these URLs from scratch and hence, TringMe provide easy to use helper functions to do this task. Helper functions can be downloaded from here.
If you are an enterprise and would like to know better how TringMe can help you reduce cost and at the same time benefit you,
please send a mail to email@example.com