The Location Detection API extracts comprehensive geographic information based on an address input. It delivers a structured response that includes several key details to accurately represent a specific location. The returned data is categorized into various components, making it easier for users to access precise insights about the location of interest.
The primary part of the response is the results matrix, which consists of detailed entries for each location. Each entry includes a breakdown of the address into essential components such as street number, route, city, administrative regions, country, and postal code. These elements are represented with both long and short names, enabling clear visualization and efficient use of space. Additionally, each component is tagged with a type to specify its role within the overall address structure, helping to differentiate between items like streets, cities, states, and countries.
In essence, the Location Detection API is a powerful tool for obtaining granular geographic data. It organizes address details into clear segments, providing valuable context for accurate interpretation.
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" : "Google Building 43",
"short_name" : "Google Building 43",
"types" :
[
"premise"
]
},
{
"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" : "Google Building 43, 1600 Amphitheatre Pkwy, Mountain View, CA 94043, USA",
"geometry" :
{
"bounds" :
{
"northeast" :
{
"lat" : 37.4218484,
"lng" : -122.0828618
},
"southwest" :
{
"lat" : 37.4212954,
"lng" : -122.0850674
}
},
"location" :
{
"lat" : 37.4215419,
"lng" : -122.0840108
},
"location_type" : "ROOFTOP",
"viewport" :
{
"northeast" :
{
"lat" : 37.42292828029149,
"lng" : -122.0826156197085
},
"southwest" :
{
"lat" : 37.4202303197085,
"lng" : -122.0853135802915
}
}
},
"place_id" : "ChIJgz9fdgK6j4AR3EL1yn1L-Mo",
"types" :
[
"premise"
]
}
],
"status" : "OK"
}
curl --location --request GET 'https://zylalabs.com/api/5147/place+locate+api/6567/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 Place Locate 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 Place Locate API returns structured geographic data, including address components, geographic coordinates, and location types. Each response contains detailed entries for locations, breaking down addresses into elements like street number, route, city, and country.
Key fields in the response include "address_components," which detail the address breakdown, "geographic coordinates" for location positioning, and "types" that categorize each address element, such as "locality" or "premise."
The response data is organized in a results matrix, where each entry contains an array of address components. Each component includes long and short names, types, and is clearly structured for easy access and interpretation.
The endpoint provides detailed address information, including street numbers, routes, localities, administrative regions, countries, and postal codes. It also includes geographic coordinates for precise location mapping.
Users can customize their requests by specifying different address parameters in the API call. This includes providing complete addresses or partial information to retrieve relevant location data based on the input.
The Place Locate API aggregates data from various authoritative geographic databases and mapping services, ensuring comprehensive coverage and reliable information for accurate location identification.
Typical use cases include location-based services, mapping applications, logistics and delivery tracking, and any application requiring precise geographic information for user addresses or business locations.
If the API returns partial or empty results, users should verify the input address for accuracy. Providing more specific details can improve response quality. Additionally, users can implement error handling to manage unexpected results effectively.
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:
97ms
Service Level:
83%
Response Time:
564ms
Service Level:
100%
Response Time:
756ms
Service Level:
100%
Response Time:
97ms
Service Level:
100%
Response Time:
664ms
Service Level:
100%
Response Time:
105ms
Service Level:
100%
Response Time:
130ms
Service Level:
100%
Response Time:
834ms
Service Level:
100%
Response Time:
616ms
Service Level:
100%
Response Time:
39ms
Service Level:
100%
Response Time:
2,586ms
Service Level:
100%
Response Time:
2,013ms
Service Level:
100%
Response Time:
2,262ms
Service Level:
100%
Response Time:
5,108ms
Service Level:
100%
Response Time:
3,512ms
Service Level:
100%
Response Time:
3,557ms
Service Level:
100%
Response Time:
2,528ms
Service Level:
100%
Response Time:
3,812ms
Service Level:
100%
Response Time:
3,465ms
Service Level:
100%
Response Time:
2,641ms