Developers and businesses can use this data to create location-based applications and services, such as travel guides, finding places like restaurants and more.
Local Search API work by accessing a database of businesses and points of interest, such as restaurants, museums, parks. The API usually provides information about the business or point of interest, such as its name, address and more. They also provide data such as latitude, longitude and other useful information.
One of the most common uses of Local Search API is for travel applications. By accessing the database of businesses and points of interest, travel guides and travel booking websites can provide users with information about the best restaurants and attractions in a particular location. This can help travelers make informed decisions about where to enjoy dining and different activities.
Local Search API are also useful for food and beverage applications. By providing information about nearby restaurants, bars and cafes, these apps can help users find the best places to eat and drink in a specific location.
In addition to travel and food and beverage applications, Local Search API can be used for many other purposes. For example, they can be used to create lists of local events, provide information about nearby parks and recreational areas, and help users find the services they need.
Overall, it is a valuable resource for developers looking to incorporate venue data into their applications or systems. With its extensive database of location information and powerful search capabilities, this API can be used to create custom search engines, directories or activity listings that provide users with the information they need to make informed decisions about where to eat, shop and more.
It will receive parameters and provide you with a JSON.
Travel guides: Can be used to provide users with information about parks, restaurants and attractions in a specific location.
Food and drink applications: Can help users find the best places to eat and drink in a specific location.
Parks and recreational areas: Can provide information about nearby parks and recreational areas.
Location: Provides information about places and their proximity to services making it easier to reach the destination.
Social media: Can be used to add location-based features to social media platforms, such as check-ins and location-based advertising.
Besides API call limitations per month, there are no other limitations.
To use this endpoint you must insert in the parameters latitude, longitude, type (coffee for example) and radius max 10.000 meters.
Get Places - Endpoint Features
| Object | Description |
|---|---|
location |
[Required] |
type |
Optional |
radius |
Optional |
{"results":[{"id":"A3178B71DBCC0FA82D4F6285B2C1C03B","name":"La vida argentina","address":"California 93657, USA","location":{"lat":36.778265,"lng":-119.417914},"types":["cafe","food","store"],"distance":4},{"id":"230079E8F476345E575149EDC2DC1170","name":"CC Jittters","address":"Sanger, CA 93657, USA","location":{"lat":36.778265,"lng":-119.417914},"types":["cafe","food"],"distance":4}]}
curl --location --request GET 'https://zylalabs.com/api/2000/local+search+api/1767/get+places?location=36.7783,-119.4179&type=cafe&radius=180' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint you must insert in the parameters the name of a place.
Get Places by Text - Endpoint Features
| Object | Description |
|---|---|
text |
[Required] |
{"results":[{"id":"4CF8CF243454935EE20AE4CB2C266F01","name":"The Getty","address":"1200 Getty Center Dr, Los Angeles, CA 90049, United States","phone_number":"+13104407300","website":"https://www.getty.edu/visit/center/","location":{"lat":34.078044,"lng":-118.474074},"types":["museum","tourist_attraction"]}]}
curl --location --request GET 'https://zylalabs.com/api/2000/local+search+api/1768/get+places+by+text?text=The getty' --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.
The "Get Places" endpoint returns information about businesses and points of interest, including their name, address, location (latitude and longitude), types, and distance from the specified coordinates. The "Get Places by Text" endpoint provides similar details but is based on a specific place name, including additional fields like phone number and website.
Key fields in the response data include "id" (unique identifier), "name" (business name), "address" (location address), "location" (latitude and longitude), "types" (categories of the place), and "distance" (proximity to the specified location).
The "Get Places" endpoint requires latitude, longitude, type (e.g., cafe), and a radius (up to 10,000 meters). The "Get Places by Text" endpoint requires the name of the place as a parameter to search for relevant results.
The response data is organized in a JSON format, with a "results" array containing individual place objects. Each object includes fields like "id," "name," "address," "location," "types," and "distance," making it easy to parse and utilize in applications.
The data is sourced from a comprehensive database of businesses and points of interest, which is regularly updated to ensure accuracy. This includes user-generated content, business listings, and verified information from various local directories.
Typical use cases include travel applications providing local attractions, food and beverage apps helping users find nearby restaurants, and social media platforms integrating location-based features for check-ins and advertising.
Users can customize requests by adjusting parameters such as latitude, longitude, type of place, and radius for the "Get Places" endpoint, or by specifying different place names for the "Get Places by Text" endpoint to refine search results.
Users can utilize the returned data by displaying it in user-friendly formats, such as maps or lists, and integrating it into applications for navigation, recommendations, or location-based services, enhancing user experience and engagement.
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:
2,053ms
Service Level:
100%
Response Time:
5,202ms
Service Level:
100%
Response Time:
3,519ms
Service Level:
100%
Response Time:
3,519ms
Service Level:
100%
Response Time:
317ms
Service Level:
83%
Response Time:
564ms
Service Level:
100%
Response Time:
1,673ms
Service Level:
100%
Response Time:
14,476ms
Service Level:
100%
Response Time:
2,429ms
Service Level:
100%
Response Time:
1,259ms
Service Level:
100%
Response Time:
764ms
Service Level:
100%
Response Time:
116ms
Service Level:
100%
Response Time:
381ms
Service Level:
100%
Response Time:
2,205ms
Service Level:
100%
Response Time:
432ms
Service Level:
100%
Response Time:
420ms
Service Level:
100%
Response Time:
1,485ms
Service Level:
100%
Response Time:
596ms
Service Level:
100%
Response Time:
344ms
Service Level:
100%
Response Time:
38ms