The Location Detection API provides detailed information about geographic locations from address input. It returns a structured response that encompasses several elements crucial to understanding the specific details of a location. The data is typically organized into several key components, which allow users to access precise details about the area of interest.
The core of the response is the results matrix, which contains individual entries about the location. Each entry provides a wealth of information, starting with the address components. This matrix breaks down the address into its fundamental parts, such as street number, route, locality, administrative areas, country and postal code. Each component is described by a long name and a short name, which facilitates both detailed visualization and compact representation. The types associated with each component indicate its role in the overall address structure, helping to distinguish between elements such as street, city, state and country.
In summary, the Location Detection API is a robust resource for detailed geographic information. It provides structured data about locations, breaking down addresses into manageable components while providing crucial geographic context. Whether for application development, mapping solutions or to enhance the user's navigation experience, the API is an indispensable tool for accurately interpreting and using location data in a variety of applications.
To use this endpoint you must specify an address in the parameter.
Geolocation - Endpoint Features
| Object | Description |
|---|---|
address |
[Required] Indicate an address such as (1600 Amphitheatre Parkway, Mountain View, CA) |
{
"results" :
[
{
"address_components" :
[
{
"long_name" : "1600",
"short_name" : "1600",
"types" :
[
"street_number"
]
},
{
"long_name" : "Amphitheatre Parkway",
"short_name" : "Amphitheatre Pkwy",
"types" :
[
"route"
]
},
{
"long_name" : "Mountain View",
"short_name" : "Mountain View",
"types" :
[
"locality",
"political"
]
},
{
"long_name" : "Santa Clara County",
"short_name" : "Santa Clara County",
"types" :
[
"administrative_area_level_2",
"political"
]
},
{
"long_name" : "California",
"short_name" : "CA",
"types" :
[
"administrative_area_level_1",
"political"
]
},
{
"long_name" : "United States",
"short_name" : "US",
"types" :
[
"country",
"political"
]
},
{
"long_name" : "94043",
"short_name" : "94043",
"types" :
[
"postal_code"
]
},
{
"long_name" : "1351",
"short_name" : "1351",
"types" :
[
"postal_code_suffix"
]
}
],
"formatted_address" : "1600 Amphitheatre Pkwy, Mountain View, CA 94043, USA",
"geometry" :
{
"location" :
{
"lat" : 37.4225022,
"lng" : -122.0847398
},
"location_type" : "ROOFTOP",
"viewport" :
{
"northeast" :
{
"lat" : 37.4239382802915,
"lng" : -122.0833973697085
},
"southwest" :
{
"lat" : 37.4212403197085,
"lng" : -122.0860953302915
}
}
},
"place_id" : "ChIJF4Yf2Ry7j4AR__1AkytDyAE",
"plus_code" :
{
"compound_code" : "CWF8+24 Mountain View, CA",
"global_code" : "849VCWF8+24"
},
"types" :
[
"street_address"
]
}
],
"status" : "OK"
}
curl --location --request GET 'https://zylalabs.com/api/5133/location+detection+api/6556/geolocation?address=1600 Amphitheatre Parkway, Mountain View, CA' --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.
To use this API users must enter a number, street name, city, state and type of address to compose a complete address.
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.
The Location Detection API identifies and retrieves geographic coordinates and location data, enabling applications to track and analyze user positions.
The Location Detection API receives location queries and provides structured output, including address components, formatted addresses, geographic coordinates, place IDs, and status information, facilitating effective location identification and mapping.
Besides the number of API calls per month, there are no other limitations.
The Location Detection API returns structured data about geographic locations, including address components, geographic coordinates, formatted addresses, and place IDs. Each entry provides detailed information about the location based on the input address.
Key fields in the response include "address_components," which breaks down the address into parts like street number, route, locality, and administrative areas, as well as "geometry," which provides geographic coordinates.
The response data is organized into a "results" array, where each entry contains "address_components" and "geometry." Each address component includes "long_name," "short_name," and "types," allowing for detailed and compact representations.
The API provides detailed information such as street numbers, routes, localities, administrative areas, countries, postal codes, and geographic coordinates, enabling comprehensive location analysis.
Users can customize their requests by specifying different address formats in the input parameter. This allows for flexibility in querying various types of locations, such as residential, commercial, or public places.
The data is sourced from a combination of public records, mapping services, and geographic databases, ensuring a broad and reliable coverage of locations.
Typical use cases include application development for navigation, mapping solutions, location-based services, and enhancing user experiences in travel and logistics applications.
If the API returns partial or empty results, users should verify the input address for accuracy. Implementing fallback mechanisms, such as suggesting similar addresses or prompting for more details, can improve result quality.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used 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.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
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, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
123ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
455ms
Service Level:
100%
Response Time:
351ms
Service Level:
100%
Response Time:
503ms
Service Level:
100%
Response Time:
46ms
Service Level:
100%
Response Time:
107ms
Service Level:
100%
Response Time:
798ms
Service Level:
100%
Response Time:
127ms
Service Level:
100%
Response Time:
285ms
Service Level:
100%
Response Time:
2,224ms
Service Level:
100%
Response Time:
236ms
Service Level:
100%
Response Time:
1,186ms
Service Level:
100%
Response Time:
853ms
Service Level:
100%
Response Time:
541ms
Service Level:
100%
Response Time:
3,469ms
Service Level:
100%
Response Time:
881ms
Service Level:
100%
Response Time:
2,073ms
Service Level:
100%
Response Time:
2,346ms
Service Level:
100%
Response Time:
3,412ms