{
"distance": "269.06km",
"duration": "3h 18min",
"steps": [
{
"direction": "depart",
"distance": "0.04km",
"duration": "0min:10s",
"instruction": "",
"location": [
10.760337,
34.797895
]
},
{
"direction": "turn",
"distance": "0.50km",
"duration": "0min:46s",
"instruction": "",
"location": [
10.760788,
34.797924
]
},
{
"direction": "new name",
"distance": "2.51km",
"duration": "3min:47s",
"instruction": "",
"location": [
10.76129,
34.802379
]
},
{
"direction": "roundabout",
"distance": "0.02km",
"duration": "0min:3s",
"instruction": "",
"location": [
10.763608,
34.824877
]
},
{
"direction": "exit roundabout",
"distance": "3.51km",
"duration": "5min:16s",
"instruction": "",
"location": [
10.763664,
34.825064
]
},
{
"direction": "roundabout",
"distance": "0.10km",
"duration": "0min:14s",
"instruction": "",
"location": [
10.760223,
34.856197
]
},
{
"direction": "exit roundabout",
"distance": "4.22km",
"duration": "3min:30s",
"instruction": "",
"location": [
10.759609,
34.856656
]
},
{
"direction": "roundabout",
"distance": "0.01km",
"duration": "0min:0s",
"instruction": "",
"location": [
10.726929,
34.883203
]
},
{
"direction": "exit roundabout",
"distance": "1.11km",
"duration": "1min:34s",
"instruction": "",
"location": [
10.726874,
34.883255
]
},
{
"direction": "fork",
"distance": "94.80km",
"duration": "1h 4min",
"instruction": "",
"location": [
10.717652,
34.889621
]
},
{
"direction": "merge",
"distance": "14.32km",
"duration": "9min:32s",
"instruction": "",
"location": [
10.563014,
35.689522
]
},
{
"direction": "fork",
"distance": "26.05km",
"duration": "18min:22s",
"instruction": "",
"location": [
10.545869,
35.814242
]
},
{
"direction": "merge",
"distance": "0.20km",
"duration": "0min:7s",
"instruction": "",
"location": [
10.436094,
36.003051
]
},
{
"direction": "new name",
"distance": "91.60km",
"duration": "1h 2min",
"instruction": "",
"location": [
10.434993,
36.004627
]
},
{
"direction": "merge",
"distance": "14.91km",
"duration": "11min:41s",
"instruction": "",
"location": [
10.327338,
36.675933
]
},
{
"direction": "off ramp",
"distance": "5.04km",
"duration": "3min:57s",
"instruction": "",
"location": [
10.200558,
36.757766
]
},
{
"direction": "roundabout",
"distance": "0.05km",
"duration": "0min:2s",
"instruction": "",
"location": [
10.169368,
36.775616
]
},
{
"direction": "exit roundabout",
"distance": "1.91km",
"duration": "1min:20s",
"instruction": "",
"location": [
10.169139,
36.775974
]
},
{
"direction": "roundabout",
"distance": "0.04km",
"duration": "0min:1s",
"instruction": "",
"location": [
10.159359,
36.790991
]
},
{
"direction": "exit roundabout",
"distance": "0.90km",
"duration": "0min:38s",
"instruction": "",
"location": [
10.159174,
36.791252
]
},
{
"direction": "off ramp",
"distance": "0.46km",
"duration": "0min:27s",
"instruction": "",
"location": [
10.150052,
36.794163
]
},
{
"direction": "turn",
"distance": "0.04km",
"duration": "0min:1s",
"instruction": "",
"location": [
10.148396,
36.797239
]
},
{
"direction": "roundabout",
"distance": "0.01km",
"duration": "0min:0s",
"instruction": "",
"location": [
10.148639,
36.797544
]
},
{
"direction": "exit roundabout",
"distance": "0.61km",
"duration": "0min:39s",
"instruction": "",
"location": [
10.148777,
36.797612
]
},
{
"direction": "turn",
"distance": "0.25km",
"duration": "0min:23s",
"instruction": "",
"location": [
10.155279,
36.798869
]
},
{
"direction": "end of road",
"distance": "1.67km",
"duration": "1min:43s",
"instruction": "",
"location": [
10.153427,
36.800345
]
},
{
"direction": "rotary",
"distance": "0.04km",
"duration": "0min:2s",
"instruction": "",
"location": [
10.137242,
36.807589
]
},
{
"direction": "exit rotary",
"distance": "0.11km",
"duration": "0min:6s",
"instruction": "",
"location": [
10.136971,
36.807783
]
},
{
"direction": "exit roundabout",
"distance": "1.62km",
"duration": "1min:29s",
"instruction": "",
"location": [
10.135729,
36.807742
]
},
{
"direction": "roundabout",
"distance": "0.04km",
"duration": "0min:2s",
"instruction": "",
"location": [
10.118673,
36.811458
]
},
{
"direction": "exit roundabout",
"distance": "0.90km",
"duration": "0min:49s",
"instruction": "",
"location": [
10.118461,
36.811736
]
},
{
"direction": "turn",
"distance": "0.56km",
"duration": "1min:7s",
"instruction": "",
"location": [
10.108981,
36.814491
]
},
{
"direction": "new name",
"distance": "0.29km",
"duration": "0min:26s",
"instruction": "",
"location": [
10.103702,
36.815367
]
},
{
"direction": "roundabout",
"distance": "0.08km",
"duration": "0min:7s",
"instruction": "",
"location": [
10.100485,
36.815644
]
},
{
"direction": "exit roundabout",
"distance": "0.07km",
"duration": "0min:16s",
"instruction": "",
"location": [
10.100497,
36.815293
]
},
{
"direction": "end of road",
"distance": "0.28km",
"duration": "1min:7s",
"instruction": "",
"location": [
10.10114,
36.815055
]
},
{
"direction": "turn",
"distance": "0.12km",
"duration": "0min:28s",
"instruction": "",
"location": [
10.102201,
36.812724
]
},
{
"direction": "end of road",
"distance": "0.07km",
"duration": "0min:16s",
"instruction": "",
"location": [
10.10313,
36.813433
]
},
{
"direction": "arrive",
"distance": "0.00km",
"duration": "0min:0s",
"instruction": "",
"location": [
10.103566,
36.813843
]
}
]
}
curl --location --request GET 'https://zylalabs.com/api/1906/tunisia+addreses+api/1609/tunisia+address+distance?start_lat=34.79778&start_lon=10.760348&end_lat=36.8139597&end_lon=10.10316736133097' --header 'Authorization: Bearer YOUR_API_KEY'
{
"distance": "268.82km",
"duration": "3h 18min",
"unit": "km"
}
curl --location --request GET 'https://zylalabs.com/api/1906/tunisia+addreses+api/1610/get+tunisia+distance+measurement?lat1=34.7977&lon1=10.76034&lat2=36.813959&lon2=10.1031673613309' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Tunisia Addreses API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
One of the main features of the Tunisia Addreses API is its distance measuring function. This allows developers to calculate distances between points and perform other location-based calculations. This is useful for applications that need to display an address based on the user's current location, or for applications that allow users to search for locations by entering coordinates.
The Tunisia Addreses API is designed to be easy to use, with a simple and intuitive API that can be easily integrated into a wide range of applications. The API is also highly scalable, meaning it can handle large volumes of requests without slowing down or crashing. Tunisia Addreses API is easy to integrate into existing applications and can be accessed via RESTful APIs. Developers can choose their preferred programming language, such as Java, Python, Ruby or PHP, and use the API to retrieve location data. By using this API, developers can create applications based on location data, such as mapping and navigation applications, location-based advertising and social media check-ins.
Overall, this API is an essential tool for developers creating location-based applications for Tunisia. With its powerful features and scalable API, the Tunisia Addreses API provides everything developers need to create cutting-edge applications based on accurate and up-to-date location data. Whether you are building a mapping application, a social networking platform or a location-based advertising platform, is the ideal tool for incorporating location-based services into your application.
It will receive parameters and provide you with a JSON.
Mapping and navigation: Developers can use the Tunisia Addreses API to create mapping and navigation applications that provide accurate and up-to-date location information.
Location-based advertising: By using this API, developers can create location-based advertising platforms that target users based on their location.
Emergency services: Emergency services can use this API to locate callers and dispatch responders to their exact location in case of an emergency.
Real estate management: Real estate companies can use to provide customers with accurate property location information.
Event planning: Event organizers can use to create maps and directions for events.
Besides the number of API calls, there is no other limitation.
The Tunisia Addresses API returns JSON data. The "GET Tunisia Address distance" endpoint provides distance, duration, and step-by-step directions between two locations. The "GET Get tunisia distance measurement" endpoint returns distance, duration, and measurement unit.
Key fields include "distance," "duration," and "steps" for the distance endpoint, while the measurement endpoint includes "distance," "duration," and "unit." Each step in the distance response also includes "direction," "distance," "duration," and "location."
Both endpoints require latitude and longitude for two locations and a distance measurement type (KM, MI, FT, or YD). Users must specify these parameters to receive accurate distance calculations.
The response data is structured in JSON format. For the distance endpoint, it includes overall distance and duration, followed by an array of "steps" detailing each segment of the route. The measurement endpoint provides a straightforward summary of distance and duration.
The Tunisia Addresses API sources its data from reliable geographic databases and mapping services. Data accuracy is maintained through regular updates and validation processes to ensure users receive current and precise location information.
Typical use cases include creating mapping applications, enabling location-based advertising, assisting emergency services in locating callers, and providing accurate property locations for real estate management.
Users can utilize the returned data by parsing the JSON response to extract relevant information, such as total distance and step-by-step directions. This data can be integrated into applications for navigation, location tracking, or user location services.
Users can customize requests by specifying different latitude and longitude pairs for various locations and selecting their preferred distance measurement unit (KM, MI, FT, YD) to tailor the output to their application's needs.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund