The Location Radius Finder API is an innovative solution that facilitates location-based searches, allowing users to discover cities and towns located within a specified geographic radius. This API leverages sophisticated geographic algorithms to provide accurate and efficient results, offering a valuable tool for applications looking to enhance their location functions.
The core of this API is its ability to perform precise location searches within a designated radius. Users can seamlessly integrate this functionality into their applications, allowing users to explore nearby cities and towns based on specific geographic coordinates. The API offers flexibility in defining the search radius, accommodating a variety of use cases and providing a customized experience for end users.
The API has a comprehensive geodatabase covering cities, towns and other populated areas around the world. This wealth of data ensures that users can explore a wide range of locations, from bustling cities to quaint villages, fostering a rich and informative experience. The broad coverage enhances the API's applicability in global scenarios, making it a valuable resource for applications with a wide user base.
In today's fast-paced digital landscape, efficiency is paramount. The API is optimized to deliver search results with minimal latency, ensuring that users receive information quickly and responsively. This efficiency helps improve the user experience, especially in applications where fast and accurate location-based searches are crucial.
Aware of the diversity of digital platforms, the API is designed for seamless integration across different environments. Whether users are working in web applications, mobile applications or other location-based services, the API facilitates integration, enhancing the overall capabilities of these platforms. This adaptability ensures that the API can be leveraged across a broad spectrum of industries and use cases.
The "Location Radius Finder API" is a valuable asset for developers who want to incorporate location-based features into their applications. Its accuracy, customization options, efficient response time and cross-platform integration capabilities make it a versatile tool applicable to a range of industries. Whether it's helping travelers explore new destinations or assisting businesses in local market exploration, this API provides a robust solution for proximity-based searches, offering a dynamic and easy-to-use experience in the realm of geographic exploration.
It will receive parameters and provide you with a JSON.
Travel Applications: Enable users to explore nearby cities and towns for travel planning, providing insights into potential destinations within a specified radius.
Real Estate Platforms: Enhance property search and location evaluation by allowing users to discover cities and towns within a defined distance from their area of interest.
Local Business Discovery: Facilitate users in exploring new markets and opportunities by incorporating nearby city and town information into applications focused on local business discovery.
Community Building Platforms: Foster connections between individuals with shared geographical interests by helping users find neighboring towns or cities through community building applications.
Logistics and Distribution Services: Optimize route planning for logistics and distribution services by identifying cities and towns within a specified radius, streamlining delivery and transportation processes.
Basic Plan: 3,000 API Calls. 100 requests per day.
Pro Plan: 6,000 API Calls. 200 requests per day.
Pro Plus Plan: 12,000 API Calls. 400 requests per day.
To use this endpoint you must indicate a latitude, longitude and radius in the parameters.
Towns Within Range - Características del Endpoint
Objeto | Descripción |
---|---|
lat |
[Requerido] |
lng |
[Requerido] |
radius |
[Requerido] |
{"status":1,"count":77,"output":[{"name":"Aberargie","countrycode":"gb","distance":12.3,"latitude":56.316667,"longitude":-3.35,"population":null},{"name":"Abernethy","countrycode":"gb","distance":10.82,"latitude":56.333333,"longitude":-3.333333,"population":"1010"},{"name":"Arngask","countrycode":"gb","distance":15.7,"latitude":56.283333,"longitude":-3.383333,"population":null},{"name":"Auchterhouse","countrycode":"gb","distance":19.19,"latitude":56.516667,"longitude":-3.066667,"population":null},{"name":"Auchtermuchty","countrycode":"gb","distance":8.39,"latitude":56.283333,"longitude":-3.216667,"population":"2023"},{"name":"Backmuir Of New Gilston","countrycode":"gb","distance":17.83,"latitude":56.266667,"longitude":-2.916667,"population":null},{"name":"Balbeggie","countrycode":"gb","distance":14.72,"latitude":56.433333,"longitude":-3.35,"population":null},{"name":"Balmerino","countrycode":"gb","distance":9.49,"latitude":56.4,"longitude":-3.033333,"population":null},{"name":"Balmullo","countrycode":"gb","distance":15.14,"latitude":56.366667,"longitude":-2.916667,"population":"1085"},{"name":"Bridge Of Earn","countrycode":"gb","distance":14.87,"latitude":56.333333,"longitude":-3.4,"population":"2231"},{"name":"Cameron Bridge","countrycode":"gb","distance":19.99,"latitude":56.183333,"longitude":-3.05,"population":null},{"name":"Ceres","countrycode":"gb","distance":14.23,"latitude":56.283333,"longitude":-2.966667,"population":"1023"},{"name":"Collace","countrycode":"gb","distance":14.78,"latitude":56.466667,"longitude":-3.283333,"population":null},{"name":"Collessie","countrycode":"gb","distance":5.84,"latitude":56.3,"longitude":-3.15,"population":null},{"name":"Craigrothie","countrycode":"gb","distance":12.54,"latitude":56.283333,"longitude":-3,"population":null},{"name":"Cupar","countrycode":"gb","distance":9.74,"latitude":56.316667,"longitude":-3.016667,"population":"8822"},{"name":"Dron","countrycode":"gb","distance":14.26,"latitude":56.316667,"longitude":-3.383333,"population":null},{"name":"Dronley","countrycode":"gb","distance":17.43,"latitude":56.5,"longitude":-3.066667,"population":null},{"name":"Dunbog","countrycode":"gb","distance":2.21,"latitude":56.333333,"longitude":-3.15,"population":null},{"name":"Dundee City","countrycode":"gb","distance":19.7,"latitude":56.466667,"longitude":-2.916667,"population":null},{"name":"Errol","countrycode":"gb","distance":4.21,"latitude":56.383333,"longitude":-3.2,"population":"1039"},{"name":"Falkland","countrycode":"gb","distance":11.61,"latitude":56.25,"longitude":-3.2,"population":"1168"},{"name":"Fife","countrycode":"gb","distance":11.37,"latitude":56.25,"longitude":-3.166667,"population":null},{"name":"Fife Conty","countrycode":"gb","distance":10.15,"latitude":56.333333,"longitude":-3,"population":null},{"name":"Fife Region","countrycode":"gb","distance":11.37,"latitude":56.25,"longitude":-3.166667,"population":null},{"name":"Fifeshire","countrycode":"gb","distance":10.15,"latitude":56.333333,"longitude":-3,"population":null},{"name":"Forgandenny","countrycode":"gb","distance":19.97,"latitude":56.333333,"longitude":-3.483333,"population":null},{"name":"Freuchie","countrycode":"gb","distance":13.23,"latitude":56.233333,"longitude":-3.15,"population":"1120"},{"name":"Gateside","countrycode":"gb","distance":13.51,"latitude":56.266667,"longitude":-3.316667,"population":null},{"name":"Gilston","countrycode":"gb","distance":17.83,"latitude":56.266667,"longitude":-2.916667,"population":null},{"name":"Glencarse","countrycode":"gb","distance":8.71,"latitude":56.366667,"longitude":-3.3,"population":null},{"name":"Glenfarg","countrycode":"gb","distance":17.54,"latitude":56.266667,"longitude":-3.4,"population":"449"},{"name":"Glenrothes","countrycode":"gb","distance":16.98,"latitude":56.2,"longitude":-3.183333,"population":"38734"},{"name":"Guildtown","countrycode":"gb","distance":19.44,"latitude":56.466667,"longitude":-3.4,"population":null},{"name":"Inchture","countrycode":"gb","distance":9.03,"latitude":56.433333,"longitude":-3.166667,"population":"715"},{"name":"Invergowrie","countrycode":"gb","distance":12.84,"latitude":56.45,"longitude":-3.05,"population":null},{"name":"Kennoway","countrycode":"gb","distance":18.26,"latitude":56.2,"longitude":-3.05,"population":"4596"},{"name":"Kilmany","countrycode":"gb","distance":10.05,"latitude":56.366667,"longitude":-3,"population":null},{"name":"Kilmaron","countrycode":"gb","distance":8.81,"latitude":56.316667,"longitude":-3.033333,"population":null},{"name":"Kilspindie","countrycode":"gb","distance":7.63,"latitude":56.4,"longitude":-3.25,"population":null},{"name":"Kinfauns","countrycode":"gb","distance":11.75,"latitude":56.366667,"longitude":-3.35,"population":null},{"name":"Kingskettle","countrycode":"gb","distance":11.69,"latitude":56.25,"longitude":-3.116667,"population":"993"},{"name":"Kinnaird","countrycode":"gb","distance":10.06,"latitude":56.433333,"longitude":-3.233333,"population":null},{"name":"Kinross County","countrycode":"gb","distance":19.43,"latitude":56.25,"longitude":-3.416667,"population":null},{"name":"Kinross-shire","countrycode":"gb","distance":19.43,"latitude":56.25,"longitude":-3.416667,"population":null},{"name":"Kirkton Of Auchterhouse","countrycode":"gb","distance":19.19,"latitude":56.516667,"longitude":-3.066667,"population":null},{"name":"Ladybank","countrycode":"gb","distance":9.66,"latitude":56.266667,"longitude":-3.133333,"population":"1519"},{"name":"Leslie","countrycode":"gb","distance":17.27,"latitude":56.2,"longitude":-3.216667,"population":null},{"name":"Leuchars","countrycode":"gb","distance":17.45,"latitude":56.383333,"longitude":-2.883333,"population":"2341"},{"name":"Leven","countrycode":"gb","distance":19.63,"latitude":56.2,"longitude":-3,"population":null},{"name":"Liff","countrycode":"gb","distance":15.35,"latitude":56.483333,"longitude":-3.083333,"population":null},{"name":"Lindores","countrycode":"gb","distance":2.51,"latitude":56.333333,"longitude":-3.183333,"population":null},{"name":"Logie","countrycode":"gb","distance":12.08,"latitude":56.366667,"longitude":-2.966667,"population":null},{"name":"Longforgan","countrycode":"gb","distance":11.21,"latitude":56.45,"longitude":-3.116667,"population":"678"},{"name":"Lundie","countrycode":"gb","distance":16.45,"latitude":56.5,"longitude":-3.15,"population":null},{"name":"Luthrie","countrycode":"gb","distance":4.8,"latitude":56.35,"longitude":-3.083333,"population":null},{"name":"Markinch","countrycode":"gb","distance":17.01,"latitude":56.2,"longitude":-3.133333,"population":null},{"name":"Milton Of Balgonie","countrycode":"gb","distance":19.15,"latitude":56.183333,"longitude":-3.1,"population":null},{"name":"Miltown","countrycode":"gb","distance":19.15,"latitude":56.183333,"longitude":-3.1,"population":null},{"name":"Monimail","countrycode":"gb","distance":6.05,"latitude":56.3,"longitude":-3.133333,"population":null},{"name":"Moonzie","countrycode":"gb","distance":6.19,"latitude":56.333333,"longitude":-3.066667,"population":null},{"name":"Muirhead","countrycode":"gb","distance":17.43,"latitude":56.5,"longitude":-3.066667,"population":null},{"name":"Muirhead Of Liff","countrycode":"gb","distance":17.43,"latitude":56.5,"longitude":-3.066667,"population":null},{"name":"New Scone","countrycode":"gb","distance":16.36,"latitude":56.416667,"longitude":-3.4,"population":"4355"},{"name":"Newburgh","countrycode":"gb","distance":5.87,"latitude":56.333333,"longitude":-3.25,"population":"1909"},{"name":"Newport","countrycode":"gb","distance":17.54,"latitude":56.433333,"longitude":-2.916667,"population":null},{"name":"Newport-On-Tay","countrycode":"gb","distance":17.54,"latitude":56.433333,"longitude":-2.916667,"population":null},{"name":"Perth","countrycode":"gb","distance":17.58,"latitude":56.4,"longitude":-3.433333,"population":"43634"},{"name":"Pitlessie","countrycode":"gb","distance":11.15,"latitude":56.266667,"longitude":-3.066667,"population":null},{"name":"Pitscottie","countrycode":"gb","distance":15.19,"latitude":56.3,"longitude":-2.933333,"population":null},{"name":"Rait","countrycode":"gb","distance":9.02,"latitude":56.416667,"longitude":-3.25,"population":null},{"name":"Saint Martins","countrycode":"gb","distance":17.47,"latitude":56.45,"longitude":-3.383333,"population":null},{"name":"Springfield","countrycode":"gb","distance":9.62,"latitude":56.283333,"longitude":-3.066667,"population":null},{"name":"Strathkinness","countrycode":"gb","distance":18.26,"latitude":56.333333,"longitude":-2.866667,"population":null},{"name":"Strathmiglo","countrycode":"gb","distance":11.53,"latitude":56.266667,"longitude":-3.266667,"population":"926"},{"name":"Woodside","countrycode":"gb","distance":19.77,"latitude":56.516667,"longitude":-3.283333,"population":null},{"name":"Wormit","countrycode":"gb","distance":13.08,"latitude":56.416667,"longitude":-2.983333,"population":null}]}
curl --location --request GET 'https://zylalabs.com/api/3134/location+radius+finder+api/3329/towns+within+range?lat=56.3522&lng=-3.1611&radius=20' --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.
To use this API users must indicate a latitude, longitude and a radius to obtain cities and towns.
The Location Radius Finder API is a powerful tool designed to facilitate location-based searches, allowing users to discover and retrieve information about places within a specified geographic radius.
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.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The "Towns Within Range" endpoint returns a JSON object containing details about towns and cities within a specified radius. This includes the name, country code, distance from the specified coordinates, latitude, longitude, and population (if available).
The key fields in the response data include "name" (town name), "countrycode" (ISO country code), "distance" (distance from the input coordinates), "latitude" (geographic latitude), "longitude" (geographic longitude), and "population" (town population, if available).
The response data is organized as a JSON object with a "status" field indicating the success of the request, a "count" field showing the number of towns found, and an "output" array containing individual town objects with their respective details.
The endpoint requires three parameters: "latitude" (the latitude of the center point), "longitude" (the longitude of the center point), and "radius" (the search radius in kilometers). Users can customize their requests by adjusting these values.
The endpoint provides information about nearby towns and cities, including their names, geographic coordinates, distances from the specified point, and population data. This information is useful for various applications, such as travel planning and local business discovery.
Data accuracy is maintained through regular updates and quality checks against reliable geographic databases. The API utilizes sophisticated geographic algorithms to ensure that the results are precise and relevant to the specified coordinates.
Typical use cases include travel applications for exploring nearby destinations, real estate platforms for evaluating property locations, local business discovery apps, and logistics services for optimizing delivery routes based on proximity to towns and cities.
Users can utilize the returned data by extracting relevant fields such as town names and distances to display nearby locations in their applications. This information can enhance user experience by providing context for travel, real estate, or community engagement.
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:
50%
Tiempo de Respuesta:
148ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
181ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
583ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
615ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
230ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
455ms
Nivel de Servicio:
50%
Tiempo de Respuesta:
2.089ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.088ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
239ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
697ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
456ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
3.690ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
456ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
456ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
456ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
294ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
319ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
466ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
183ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
417ms