The Geographic Distance Tracker API is a robust tool designed to calculate and deliver travel distances and durations between various starting and ending locations. It is an invaluable asset for users seeking to incorporate geographic data into their applications, improving decision-making in areas like logistics, travel planning, and transportation management.
With the Geographic Distance Tracker API, users can input parameters such as origin and destination addresses. The API processes these inputs and generates a structured response containing key route details between the specified locations. The output typically includes a list of origin and destination addresses, clearly presenting the route information.
In conclusion, whether for personal use or as part of an application, the Geographic Distance Tracker API streamlines route planning and travel time estimation. Its comprehensive and structured outputs make it a vital resource for integrating geographic data into systems, enhancing both functionality and user experience in today’s interconnected world.
To use this endpoint you must indicate 2 locations in the parameters.
For example:
New York City, NY
Washington, DC
Distance Data - Endpoint Features
| Object | Description |
|---|---|
destinations |
[Required] |
origins |
[Required] |
{
"destination_addresses" :
[
"New York, NY, USA"
],
"origin_addresses" :
[
"Washington, DC, USA"
],
"rows" :
[
{
"elements" :
[
{
"distance" :
{
"text" : "362 km",
"value" : 361721
},
"duration" :
{
"text" : "3 hours 51 mins",
"value" : 13875
},
"status" : "OK"
}
]
}
],
"status" : "OK"
}
curl --location --request GET 'https://zylalabs.com/api/5453/geographic+distance+tracker+api/7077/distance+data?destinations=New York City, NY&origins=Washington, DC' --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.
To use this API users must indicate 2 locations to measure the distance.
The Geographic Distance Tracker API calculates and monitors the distance between two or more locations, providing real-time updates on travel time, distance covered, and estimated arrival, enhancing logistics and travel management.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
Receives origin and destination inputs and provides calculated distance, travel time, and status between specified locations efficiently.
Besides the number of API calls per month, there are no other limitations.
The Distance Data endpoint returns travel distance, duration, and status between specified origin and destination locations. It includes detailed route information structured in a JSON format.
Key fields in the response include "distance" (with "text" and "value"), "duration" (with "text" and "value"), "origin_addresses," "destination_addresses," and "status," which indicates the success of the request.
The response data is organized into arrays for "origin_addresses" and "destination_addresses," with a "rows" array containing "elements" that detail distance and duration for each route, making it easy to parse.
Users must provide two parameters: the origin and destination locations. These can be specified as addresses, cities, or geographic coordinates to customize the request.
The endpoint provides information on travel distance, estimated travel time, and the status of the request, allowing users to assess routes for logistics or travel planning.
Data accuracy is maintained through the use of reliable geographic databases and continuous updates to ensure that distance and duration calculations reflect current road conditions and routes.
Typical use cases include logistics planning, travel itinerary creation, route optimization for delivery services, and personal travel planning, helping users make informed decisions based on distance and time.
Users can utilize the returned data by integrating it into applications for route visualization, travel time estimation, or logistics management, enhancing user experience with real-time geographic insights.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
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:
84ms
Service Level:
100%
Response Time:
169ms
Service Level:
100%
Response Time:
105ms
Service Level:
100%
Response Time:
159ms
Service Level:
100%
Response Time:
188ms
Service Level:
100%
Response Time:
142ms
Service Level:
100%
Response Time:
445ms
Service Level:
100%
Response Time:
487ms
Service Level:
100%
Response Time:
120ms
Service Level:
100%
Response Time:
537ms
Service Level:
99%
Response Time:
14,190ms
Service Level:
100%
Response Time:
6,275ms
Service Level:
99%
Response Time:
5,882ms
Service Level:
100%
Response Time:
7,480ms
Service Level:
100%
Response Time:
424ms
Service Level:
100%
Response Time:
10,625ms
Service Level:
100%
Response Time:
1,931ms
Service Level:
100%
Response Time:
1,870ms
Service Level:
100%
Response Time:
2,925ms
Service Level:
100%
Response Time:
2,485ms