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.
To use this endpoint you must indicate the latitude and longitude of the 2 locations and the type of distance measurement KM or MI.
Tunisia Address distance - Endpoint Features
Object | Description |
---|---|
start_lat |
[Required] |
start_lon |
[Required] |
end_lat |
[Required] |
end_lon |
[Required] |
{
"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'
To use this endpoint you must indicate the latitude and longitude of the 2 locations and the type of distance measurement. km, mi, ft, and yd.
Get tunisia distance measurement - Endpoint Features
Object | Description |
---|---|
lat1 |
[Required] |
lon1 |
[Required] |
lat2 |
[Required] |
lon2 |
[Required] |
{
"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'
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 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.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
1,316ms
Service Level:
100%
Response Time:
928ms
Service Level:
100%
Response Time:
424ms
Service Level:
100%
Response Time:
1,704ms
Service Level:
100%
Response Time:
1,111ms
Service Level:
100%
Response Time:
343ms
Service Level:
100%
Response Time:
2,082ms
Service Level:
100%
Response Time:
527ms
Service Level:
100%
Response Time:
502ms
Service Level:
100%
Response Time:
509ms
Service Level:
100%
Response Time:
9,717ms
Service Level:
100%
Response Time:
4,089ms
Service Level:
100%
Response Time:
10,132ms
Service Level:
100%
Response Time:
577ms
Service Level:
100%
Response Time:
8,024ms
Service Level:
100%
Response Time:
1,748ms
Service Level:
100%
Response Time:
7,443ms
Service Level:
100%
Response Time:
8,515ms
Service Level:
100%
Response Time:
1,486ms
Service Level:
100%
Response Time:
354ms