Developers can use the Ethiopia Location API to create geolocation-based services that bring value to their users. For example, they can use the API to create transportation applications that match passengers with drivers based on their location. They can also use the API to create delivery services that accurately locate customers and deliver products to their doorstep.
Ethiopia Location API can also be used to create weather applications that provide users with accurate and up-to-date weather information based on their location. Developers can also use the API to create maps and navigation applications that provide users with turn-by-turn directions to their destination.
Ethiopia Location 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.
In addition to providing location data, this API also offers developers access to various location-based services, such as reverse geocoding. Reverse geocoding is the process of converting longitude and latitude coordinates into an address. Geofencing is the process of creating a virtual boundary around a specific location, and developers can use this feature to trigger location-based notifications, alerts or actions.
In conclusion, is a powerful tool for developers who want to create location-based services for the Morocco market. The API provides accurate and up-to-date location data, as well as access to a wide variety of location-based services and advanced features. With the Morocco Location API, developers can create innovative and useful applications that deliver value to users and drive business growth.
It will receive parameters and provide you with a JSON.
Navigation and mapping: The Ethiopia location API can be used by mapping and navigation applications to provide accurate and up-to-date location information to users in Ethiopia.
Geolocation-based advertising: Marketers and advertisers can use Ethiopia's location API to send targeted and personalized advertising messages to users in specific locations in Ethiopia.
Tourism and hospitality: Companies in the tourism and hospitality sector can use the Ethiopia Location API to provide location-based information to tourists and travelers in Ethiopia.
Real estate and property management: Real estate agents, property managers and rental services can use the Ethiopia Location API to display accurate property location data.
Transportation and logistics: companies involved in transportation and logistics, such as carriers, logistics providers and fleet management services, can use the Ethiopia location API to track vehicles, optimize routes and manage shipments. This can help improve transportation efficiency and streamline logistics operations in Ethiopia.
Besides the number of API calls, there is no other limitation.
To use this endpoint all you have to do is to insert in the parameters the latitude, longitude of 2 locations with their unit of measure km and mi.
Get Ethiopia route - Endpoint Features
Object | Description |
---|---|
start_lat |
[Required] |
start_lon |
[Required] |
end_lat |
[Required] |
end_lon |
[Required] |
distance_unit |
[Optional] |
{
"distance": "790.08km",
"duration": "9h 37min",
"steps": [
{
"direction": "depart",
"distance": "0.06km",
"duration": "0min:8s",
"instruction": "",
"location": [
39.447449,
13.506198
]
},
{
"direction": "turn",
"distance": "0.29km",
"duration": "0min:32s",
"instruction": "",
"location": [
39.447837,
13.505833
]
},
{
"direction": "fork",
"distance": "3.01km",
"duration": "4min:33s",
"instruction": "",
"location": [
39.449728,
13.507557
]
},
{
"direction": "turn",
"distance": "0.33km",
"duration": "0min:29s",
"instruction": "",
"location": [
39.474078,
13.496082
]
},
{
"direction": "fork",
"distance": "0.07km",
"duration": "0min:6s",
"instruction": "",
"location": [
39.47304,
13.493251
]
},
{
"direction": "new name",
"distance": "0.47km",
"duration": "0min:43s",
"instruction": "",
"location": [
39.473192,
13.492674
]
},
{
"direction": "roundabout",
"distance": "0.00km",
"duration": "0min:0s",
"instruction": "",
"location": [
39.476197,
13.489558
]
},
{
"direction": "exit roundabout",
"distance": "0.05km",
"duration": "0min:2s",
"instruction": "",
"location": [
39.476195,
13.489551
]
},
{
"direction": "new name",
"distance": "1.38km",
"duration": "1min:16s",
"instruction": "",
"location": [
39.476123,
13.489076
]
},
{
"direction": "new name",
"distance": "6.90km",
"duration": "6min:22s",
"instruction": "",
"location": [
39.473779,
13.477536
]
},
{
"direction": "roundabout",
"distance": "0.08km",
"duration": "0min:4s",
"instruction": "",
"location": [
39.531903,
13.477567
]
},
{
"direction": "exit roundabout",
"distance": "1.45km",
"duration": "1min:46s",
"instruction": "",
"location": [
39.532243,
13.477102
]
},
{
"direction": "turn",
"distance": "6.97km",
"duration": "4min:55s",
"instruction": "",
"location": [
39.544173,
13.474254
]
},
{
"direction": "exit roundabout",
"distance": "71.28km",
"duration": "51min:28s",
"instruction": "",
"location": [
39.553046,
13.421295
]
},
{
"direction": "continue",
"distance": "2.79km",
"duration": "1min:58s",
"instruction": "",
"location": [
39.517759,
12.935746
]
},
{
"direction": "end of road",
"distance": "33.85km",
"duration": "23min:54s",
"instruction": "",
"location": [
39.520638,
12.917813
]
},
{
"direction": "continue",
"distance": "16.81km",
"duration": "11min:52s",
"instruction": "",
"location": [
39.547575,
12.789532
]
},
{
"direction": "new name",
"distance": "22.77km",
"duration": "16min:7s",
"instruction": "",
"location": [
39.530006,
12.669861
]
},
{
"direction": "new name",
"distance": "101.21km",
"duration": "1h 16min",
"instruction": "",
"location": [
39.512121,
12.523909
]
},
{
"direction": "roundabout",
"distance": "0.03km",
"duration": "0min:3s",
"instruction": "",
"location": [
39.604059,
11.833133
]
},
{
"direction": "exit roundabout",
"distance": "79.13km",
"duration": "55min:52s",
"instruction": "",
"location": [
39.603937,
11.832966
]
},
{
"direction": "turn",
"distance": "11.52km",
"duration": "8min:8s",
"instruction": "",
"location": [
39.635126,
11.385683
]
},
{
"direction": "roundabout",
"distance": "0.01km",
"duration": "0min:0s",
"instruction": "",
"location": [
39.677208,
11.312918
]
},
{
"direction": "exit roundabout",
"distance": "18.18km",
"duration": "12min:50s",
"instruction": "",
"location": [
39.677208,
11.312814
]
},
{
"direction": "turn",
"distance": "5.36km",
"duration": "3min:47s",
"instruction": "",
"location": [
39.679631,
11.161257
]
},
{
"direction": "new name",
"distance": "1.75km",
"duration": "1min:14s",
"instruction": "",
"location": [
39.649545,
11.145884
]
},
{
"direction": "roundabout",
"distance": "0.03km",
"duration": "0min:1s",
"instruction": "",
"location": [
39.639319,
11.144441
]
},
{
"direction": "exit roundabout",
"distance": "1.15km",
"duration": "0min:50s",
"instruction": "",
"location": [
39.639072,
11.144488
]
},
{
"direction": "end of road",
"distance": "0.91km",
"duration": "0min:38s",
"instruction": "",
"location": [
39.631919,
11.140306
]
},
{
"direction": "new name",
"distance": "0.62km",
"duration": "0min:25s",
"instruction": "",
"location": [
39.633217,
11.132305
]
},
{
"direction": "turn",
"distance": "1.08km",
"duration": "0min:46s",
"instruction": "",
"location": [
39.634592,
11.126899
]
},
{
"direction": "roundabout",
"distance": "0.05km",
"duration": "0min:2s",
"instruction": "",
"location": [
39.632634,
11.117456
]
},
{
"direction": "exit roundabout",
"distance": "20.29km",
"duration": "14min:19s",
"instruction": "",
"location": [
39.632706,
11.117179
]
},
{
"direction": "roundabout",
"distance": "0.05km",
"duration": "0min:2s",
"instruction": "",
"location": [
39.739075,
11.085809
]
},
{
"direction": "exit roundabout",
"distance": "0.73km",
"duration": "0min:31s",
"instruction": "",
"location": [
39.739388,
11.085782
]
},
{
"direction": "roundabout",
"distance": "0.01km",
"duration": "0min:0s",
"instruction": "",
"location": [
39.743435,
11.080992
]
},
{
"direction": "exit roundabout",
"distance": "2.40km",
"duration": "1min:41s",
"instruction": "",
"location": [
39.743545,
11.080968
]
},
{
"direction": "roundabout",
"distance": "0.03km",
"duration": "0min:1s",
"instruction": "",
"location": [
39.743282,
11.059903
]
},
{
"direction": "exit roundabout",
"distance": "242.08km",
"duration": "2h 50min",
"instruction": "",
"location": [
39.743329,
11.059686
]
},
{
"direction": "roundabout",
"distance": "0.03km",
"duration": "0min:1s",
"instruction": "",
"location": [
39.533064,
9.678319
]
},
{
"direction": "exit roundabout",
"distance": "111.52km",
"duration": "1h 18min",
"instruction": "",
"location": [
39.532945,
9.678171
]
},
{
"direction": "rotary",
"distance": "0.05km",
"duration": "0min:2s",
"instruction": "",
"location": [
38.878632,
9.057353
]
},
{
"direction": "exit rotary",
"distance": "2.99km",
"duration": "3min:26s",
"instruction": "",
"location": [
38.878295,
9.057124
]
},
{
"direction": "continue",
"distance": "5.80km",
"duration": "5min:21s",
"instruction": "",
"location": [
38.862063,
9.041738
]
},
{
"direction": "roundabout",
"distance": "0.04km",
"duration": "0min:2s",
"instruction": "",
"location": [
38.818298,
9.024036
]
},
{
"direction": "exit roundabout",
"distance": "1.95km",
"duration": "1min:48s",
"instruction": "",
"location": [
38.818063,
9.02386
]
},
{
"direction": "rotary",
"distance": "0.04km",
"duration": "0min:2s",
"instruction": "",
"location": [
38.801607,
9.021603
]
},
{
"direction": "exit rotary",
"distance": "0.67km",
"duration": "0min:41s",
"instruction": "",
"location": [
38.801294,
9.021809
]
},
{
"direction": "turn",
"distance": "0.43km",
"duration": "0min:26s",
"instruction": "",
"location": [
38.795923,
9.024703
]
},
{
"direction": "turn",
"distance": "1.56km",
"duration": "1min:26s",
"instruction": "",
"location": [
38.794794,
9.021085
]
},
{
"direction": "roundabout",
"distance": "0.05km",
"duration": "0min:2s",
"instruction": "",
"location": [
38.780883,
9.023616
]
},
{
"direction": "exit roundabout",
"distance": "0.43km",
"...
curl --location --request GET 'https://zylalabs.com/api/1926/ethiopia+location+api/1636/get+ethiopia+route?start_lat=13.50733412686565&start_lon=39.44712684241014&end_lat=8.97207888444046&end_lon=38.733015539854&distance_unit=km' --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, yd and ft.
Get Ethiopia distance - Endpoint Features
Object | Description |
---|---|
lat1 |
[Required] |
lon1 |
[Required] |
lat2 |
[Required] |
lon2 |
[Required] |
unit |
[Optional] |
{
"distance": "790.08km",
"duration": "9h 37min",
"unit": "km"
}
curl --location --request GET 'https://zylalabs.com/api/1926/ethiopia+location+api/1637/get+ethiopia+distance?lat1=13.50733412686565&lon1=39.44712684241014&lat2=8.97207888444046&lon2=38.733015539854&unit=km' --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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
The "Get Ethiopia route" endpoint returns distance, duration, and detailed step-by-step navigation instructions. The "Get Ethiopia distance" endpoint provides the distance between two locations, duration, and the unit of measurement used.
Key fields include "distance," "duration," and "steps" for the route endpoint, while the distance endpoint includes "distance," "duration," and "unit." Each step in the route includes "direction," "distance," "duration," and "location."
Both endpoints require latitude and longitude for two locations. The route endpoint also requires a unit of measure (km or mi), while the distance endpoint accepts additional units like yd and ft.
The response data is structured in JSON format. For the route endpoint, it includes an array of steps detailing navigation instructions, while the distance endpoint provides a straightforward summary of distance and duration.
The Ethiopia Location API sources its data from various geolocation databases and mapping services, ensuring comprehensive coverage of Ethiopian geography and infrastructure.
Common use cases include navigation apps providing turn-by-turn directions, logistics companies optimizing delivery routes, and tourism apps offering location-based information to travelers.
Users can customize requests by specifying different latitude and longitude pairs and selecting their preferred unit of measurement for distance calculations, allowing for tailored responses based on user needs.
Users can leverage the distance and duration data for route planning, while the step-by-step instructions can be integrated into navigation systems to guide users accurately to their destinations.
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:
727ms
Service Level:
100%
Response Time:
624ms
Service Level:
100%
Response Time:
1,163ms
Service Level:
100%
Response Time:
502ms
Service Level:
100%
Response Time:
1,704ms
Service Level:
100%
Response Time:
396ms
Service Level:
100%
Response Time:
715ms
Service Level:
100%
Response Time:
657ms
Service Level:
100%
Response Time:
2,065ms