Terms and Privacy •
Using the Taximail APIBase URLAll the Taximail API's are accessed through a base URL which is - api.taximail.com. All API calls should be made over HTTPS. It works with any language that has an HTTP library, such as cURL, urllib. For using the Taximail API directly in your browser, you can make an API request like follows:
You can try using the above API by clicking this this link from your web browser. Normally, You will get the response as below:
•••
HTTP MethodsThe latest version of Taximail API uses the standard HTTP methods to perform various actions on a resource. HTTP defines a set of request methods to indicate the desired action to be performed for a given resource.
•••
Generate a session_id from Authentication API
Most of the Taximail API requests require the use of session_id which your app can generate by two ways:
This section will cover how to generate a session_id from Authentication API using the API Key and Secret Key. Firstly, you need to generate API Key and Secret Key from the Integration module API Key
POSThttps://api.taximail.com/v2/user/login
Example RequestFollowing is an example request which can be made.
Example ResultOnce you execute the above API call, you will receive either a success data or error data in JSON format
You can authenticate by selecting Basic Auth and specifying the username and password parameters in the Authentication API and then specify the description as the API key and Secret key:
POSThttps://api.taximail.com/v2/transactional
Example from the Authentication in Postman application.
Example ResultOnce you execute the above API call, you will receive either a success data or error data in JSON format
Response Code
Authentication is required for all endpoints in the Taximail public API. The API accepts HTTP Bearer authentication for all endpoints. API versionsThe Taximail API has multiple versions available to access at any one time. Each version contains a set of core fields and edge operations. We guarantee that those core APIs will be available and un-modified in that version for at least 2 years from release. The platform changelog can tell you which versions are currently available. Everything outside of these core APIs is called extended APIs. These APIs are still accessed through versioned paths. They can also be potentially modified or removed at any time, subject to 120-day migrations that would be announced on our platform roadmap. Alternatively, they may simply be included in the next available API version. •••
Next Steps
|