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 - Características del Endpoint
Objeto | Descripción |
---|---|
start_lat |
[Requerido] |
start_lon |
[Requerido] |
end_lat |
[Requerido] |
end_lon |
[Requerido] |
distance_unit |
Opcional |
{
"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 - Características del Endpoint
Objeto | Descripción |
---|---|
lat1 |
[Requerido] |
lon1 |
[Requerido] |
lat2 |
[Requerido] |
lon2 |
[Requerido] |
unit |
Opcional |
{
"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'
Encabezado | Descripción |
---|---|
Autorización
|
[Requerido] Debería ser Bearer access_key . Consulta "Tu Clave de Acceso a la API" arriba cuando estés suscrito. |
Sin compromiso a largo plazo. Mejora, reduce o cancela en cualquier momento. La Prueba Gratuita incluye hasta 50 solicitudes.
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 es como una gran tienda de APIs, donde puedes encontrar miles de ellas en un solo lugar. También ofrecemos soporte dedicado y monitoreo en tiempo real de todas las APIs. Una vez que te registres, puedes elegir qué APIs quieres usar. Solo recuerda que cada API necesita su propia suscripción. Pero si te suscribes a varias, usarás la misma clave para todas, lo que hace todo más fácil para ti.
Los precios se muestran en USD (dólar estadounidense), EUR (euro), CAD (dólar canadiense), AUD (dólar australiano) y GBP (libra esterlina). Aceptamos todas las principales tarjetas de débito y crédito. Nuestro sistema de pago utiliza la última tecnología de seguridad y está respaldado por Stripe, una de las compañías de pago más confiables del mundo. Si tienes algún problema para pagar con tarjeta, contáctanos en [email protected]
Además, si ya tienes una suscripción activa en cualquiera de estas monedas (USD, EUR, CAD, AUD, GBP), esa moneda se mantendrá para suscripciones posteriores. Puedes cambiar la moneda en cualquier momento siempre que no tengas suscripciones activas.
La moneda local que aparece en la página de precios se basa en el país de tu dirección IP y se proporciona solo como referencia. Los precios reales están en USD (dólar estadounidense). Cuando realices un pago, el cargo aparecerá en tu estado de cuenta en USD, incluso si ves el monto equivalente en tu moneda local en nuestro sitio web. Esto significa que no puedes pagar directamente en tu moneda local.
Ocasionalmente, un banco puede rechazar el cargo debido a sus configuraciones de protección contra fraude. Te sugerimos comunicarte con tu banco primero para verificar si están bloqueando nuestros cargos. También puedes acceder al Portal de Facturación y cambiar la tarjeta asociada para realizar el pago. Si esto no funciona y necesitas más ayuda, por favor contacta a nuestro equipo en [email protected]
Los precios se determinan mediante una suscripción recurrente mensual o anual, dependiendo del plan elegido.
Las llamadas a la API se descuentan de tu plan en base a solicitudes exitosas. Cada plan incluye una cantidad específica de llamadas que puedes realizar por mes. Solo las llamadas exitosas, indicadas por una respuesta con estado 200, se contarán en tu total. Esto asegura que las solicitudes fallidas o incompletas no afecten tu cuota mensual.
Zyla API Hub funciona con un sistema de suscripción mensual recurrente. Tu ciclo de facturación comenzará el día en que compres uno de los planes de pago, y se renovará el mismo día del mes siguiente. Así que recuerda cancelar tu suscripción antes si quieres evitar futuros cargos.
Para actualizar tu plan de suscripción actual, simplemente ve a la página de precios de la API y selecciona el plan al que deseas actualizarte. La actualización será instantánea, permitiéndote disfrutar inmediatamente de las funciones del nuevo plan. Ten en cuenta que las llamadas restantes de tu plan anterior no se transferirán al nuevo plan, por lo que debes considerar esto al actualizar. Se te cobrará el monto total del nuevo plan.
Para verificar cuántas llamadas a la API te quedan en el mes actual, revisa el campo 'X-Zyla-API-Calls-Monthly-Remaining' en el encabezado de la respuesta. Por ejemplo, si tu plan permite 1,000 solicitudes por mes y has usado 100, este campo mostrará 900 llamadas restantes.
Para ver el número máximo de solicitudes a la API que permite tu plan, revisa el encabezado de la respuesta 'X-Zyla-RateLimit-Limit'. Por ejemplo, si tu plan incluye 1,000 solicitudes por mes, este encabezado mostrará 1,000.
El encabezado 'X-Zyla-RateLimit-Reset' muestra el número de segundos hasta que tu límite se restablezca. Esto te indica cuándo tu conteo de solicitudes se reiniciará. Por ejemplo, si muestra 3,600, significa que faltan 3,600 segundos para que el límite se restablezca.
Sí, puedes cancelar tu plan en cualquier momento desde tu cuenta, seleccionando la opción de cancelación en la página de Facturación. Ten en cuenta que las actualizaciones, degradaciones y cancelaciones tienen efecto inmediato. Además, al cancelar ya no tendrás acceso al servicio, incluso si te quedaban llamadas en tu cuota.
Puedes contactarnos a través de nuestro canal de chat para recibir asistencia inmediata. Siempre estamos en línea de 8 a. m. a 5 p. m. (EST). Si nos contactas fuera de ese horario, te responderemos lo antes posible. Además, puedes escribirnos por correo electrónico a [email protected]
Para darte la oportunidad de probar nuestras APIs sin compromiso, ofrecemos una prueba gratuita de 7 días que te permite realizar hasta 50 llamadas a la API sin costo. Esta prueba solo se puede usar una vez, por lo que recomendamos aplicarla a la API que más te interese. Aunque la mayoría de nuestras APIs ofrecen prueba gratuita, algunas pueden no hacerlo. La prueba finaliza después de 7 días o cuando realices 50 solicitudes, lo que ocurra primero. Si alcanzas el límite de 50 solicitudes durante la prueba, deberás "Iniciar tu Plan de Pago" para continuar haciendo solicitudes. Puedes encontrar el botón "Iniciar tu Plan de Pago" en tu perfil bajo Suscripción -> Elige la API a la que estás suscrito -> Pestaña de Precios. Alternativamente, si no cancelas tu suscripción antes del día 7, tu prueba gratuita finalizará y tu plan se cobrará automáticamente, otorgándote acceso a todas las llamadas a la API especificadas en tu plan. Ten esto en cuenta para evitar cargos no deseados.
Después de 7 días, se te cobrará el monto total del plan al que estabas suscrito durante la prueba. Por lo tanto, es importante cancelar antes de que finalice el periodo de prueba. No se aceptan solicitudes de reembolso por olvidar cancelar a tiempo.
Cuando te suscribes a una prueba gratuita de una API, puedes realizar hasta 50 llamadas. Si deseas realizar más llamadas después de este límite, la API te pedirá que "Inicies tu Plan de Pago". Puedes encontrar el botón "Iniciar tu Plan de Pago" en tu perfil bajo Suscripción -> Elige la API a la que estás suscrito -> Pestaña de Precios.
Las Órdenes de Pago se procesan entre el día 20 y el 30 de cada mes. Si envías tu solicitud antes del día 20, tu pago será procesado dentro de ese período.
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.316ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
727ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
345ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
977ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
502ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
624ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.551ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.614ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.704ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.065ms