About the API:
The Taxi Fare Calculator API allows users to calculate the estimated cost of a taxi ride between two locations. The API returns the estimated fare, distance, and duration of the trip, as well as any applicable surcharges or fees. Users can input their starting and ending locations. This API is useful for travelers planning a trip by taxi or for businesses looking to offer a taxi fare calculator on their website or app.
Pass the departure and arrival coordinates and receive the estimated duration and fare for the trip.
A taxi company or ride-hailing app could use the API to provide fare estimates to its users before they request a ride.
A travel website or app could use the API to help tourists plan their transportation expenses while on vacation.
A transportation company could use the API to help its users estimate the cost of a taxi ride as part of a multi-modal journey.
A real estate website or app could use the API to help home buyers and renters estimate the cost of commuting to work or other destinations from a given property.
A website or app that helps users plan events or parties could use the API to estimate the cost of providing transportation for attendees.
A transportation analytics platform could use the API to gather and analyze data on taxi fares in different cities or regions.
Besides the number of API calls per month, there is a limitation of 1 request per second.
Search fares by geo coordinates
Taxi Fare Calculator - Endpoint Features
| Object | Description |
|---|---|
dep_lat |
[Required] Latitude of departure point |
dep_lng |
[Required] Longitude of departure point |
arr_lat |
[Required] Latitude of arrival point |
arr_lng |
[Required] Longitude of arrival point |
{"headers":{"response_time":607,"response_timestamp":"2025-01-18T13:20:39.740Z","api":"taxicalculator","response_id":104970},"journey":{"city_name":"Berlin","department":"Lausitzer Pl. 5, 10997 Berlin, Deutschland","arrival":"Dahlwitzer Landstraße 181, 12587 Berlin, Deutschland","duration":34,"distance":21,"fares":[{"name":"by Day","price_in_cents":5250,"estimated":false},{"name":"by Night","price_in_cents":"n/a","estimated":false}]}}
curl --location --request GET 'https://zylalabs.com/api/876/taxi+fare+calculator+api/663/taxi+fare+calculator?dep_lat=52.5&dep_lng=13.43&arr_lat=52.47&arr_lng=13.63' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The API returns estimated taxi fare, distance, duration of the trip, and any applicable surcharges or fees based on the provided departure and arrival coordinates.
Key fields include "city_name," "duration," "distance," and "fares," which contains fare details such as "name" and "price_in_cents."
The response is structured in a JSON format, with a "headers" section for metadata and a "journey" section detailing the trip's specifics, including fare estimates.
The primary parameters are the geo coordinates for the departure and arrival locations. Users can customize requests by providing accurate latitude and longitude values.
The endpoint provides information on estimated fares, trip duration, distance, and any applicable surcharges, helping users plan their taxi rides effectively.
Data accuracy is maintained through regular updates and validation against real-world taxi fare structures and local regulations, ensuring reliable fare estimates.
Typical use cases include fare estimation for ride-hailing apps, travel planning for tourists, and cost analysis for real estate commuting assessments.
Users can utilize the fare estimates and trip details to budget for transportation costs, compare options, and enhance user experience in travel-related applications.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,290ms
Service Level:
100%
Response Time:
120ms
Service Level:
100%
Response Time:
203ms
Service Level:
100%
Response Time:
345ms
Service Level:
100%
Response Time:
388ms
Service Level:
100%
Response Time:
826ms
Service Level:
100%
Response Time:
146ms
Service Level:
100%
Response Time:
2,223ms
Service Level:
100%
Response Time:
646ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
693ms
Service Level:
100%
Response Time:
491ms
Service Level:
100%
Response Time:
693ms
Service Level:
100%
Response Time:
693ms
Service Level:
100%
Response Time:
826ms
Service Level:
100%
Response Time:
388ms
Service Level:
100%
Response Time:
0ms