You need to let users search what’s nearby, show an address for a pin on a map, and pull photos and reviews for a place—this week. By the end of this article you’ll be able to call location endpoints on Zyla API Hub’s Google Maps API to search a place, resolve “what is here” by lat/lng, and fetch photos and reviews for a place ID.
What this API gives you
The Google Maps API on Zyla provides:
- Search: find places by text query with coordinates, address, photos, and place_id.
- What is here: reverse-lookup address and nearby business context for a lat/lng.
- Place photos: retrieve photos for a place using its Place ID.
- Place reviews: retrieve user reviews for a place by Place ID.
These endpoints power location search, maps “tap-on-map” experiences, and place detail views in web and mobile apps.
Getting started on Zyla API Hub
Open the API page on Zyla API Hub, click Subscribe or Start 7-day trial when available, and get your API key. Zyla runs on a subscription and quota model (not pay-per-call). For this API, you can start with a 7-day trial or 50 requests—check the API page for current access options and pricing.
Authenticate every request with an HTTP header:
- Authorization: Bearer YOUR_API_KEY
The marketplace aggregates more than 10,000 public APIs; one account and one API key work across services, with consistent billing. Create a free account and get a key directly from the API page: Start 7-day trial on Google Maps API.
Endpoints you’ll use
1) Search
Find places by text. The example below searches for “Berlin” at a given zoom level.
Method: GET
URL: https://zylalabs.com/api/10107/google-maps-api/19301/search
Query parameters (from sample): query, zoom
curl -s -X GET "https://zylalabs.com/api/10107/google-maps-api/19301/search?query=Berlin&zoom=13" \
-H "Authorization: Bearer YOUR_API_KEY"
Sample response:
{
"status": "ok",
"data": [
{
"business_id": "0x47a84e373f035901:0x42120465b5e3b70",
"phone_number": null,
"name": "Berlin",
"full_address": "Berlin, Germany",
"full_address_array": [
"Germany"
],
"latitude": 52.520006599999995,
"longitude": 13.404954,
"review_count": null,
"rating": null,
"timezone": "Europe/Berlin",
"website": null,
"place_id": "ChIJAVkDPzdOqEcRcDteW0YgIQQ",
"place_link": "https://www.google.com/maps/place/data=!3m1!4b1!4m2!3m1!1s0x47a84e373f035901:0x42120465b5e3b70",
"types": null,
"price_level": null,
"working_hours": [],
"city": "Berlin, Germany",
"is_claimed": false,
"verified": true,
"is_permanently_closed": false,
"is_temporarily_closed": false,
"photos": [
{
"src": "https://lh3.googleusercontent.com/grass-cs/AABkmLffehkFWQeKJcoSb-1YW6L8asBOURQlYg7lDTzlg-TUUjHcP_iZA3YCo6lc1vSKHWpq9OwDIyiwB46OCe5IRwpsCCci5585tr4m6FnBlKPsaS3WVsEA1la8CVcIMhti5jyCmVBW=w203-h126-k-no",
"max_size": [
4963,
3102
],
"min_size": [
203,
100
]
},
{
"src": "https://lh3.googleusercontent.com/grass-cs/AABkmLcK-9P8aapCvGa0e5zeC2wBQm0Y01228VvLazWmPdE7yc_geBaO7DanSWf59BJSHospUgsiE7K6-VjWpB8b3c03ZfvnHzx3LwM50nvfCQ-DCaXA_fqLDhHnTrbcYAfCIzDumboTPQ=w203-h152-k-no",
"max_size": [
12000,
9000
],
"min_size": [
203,
100
]
},
{
"src": "https://lh3.googleusercontent.com/grass-cs/AABkmLfHzbwqyGh-qbjub4sgIBqFw1JqsU9wA-fOOAcEaQi24vqQnx47CebTSe9LxHMr6MfXW2M62qX94rtnpMeS9oFWfll0cW1avvFvgg1PWymyOTAen250DP6tK-Q_cVGIGL003WPOow=w203-h152-k-no",
"max_size": [
4032,
3024
],
"min_size": [
203,
100
]
},…
What you’ll actually use:
- name, full_address, city: show result titles and summaries.
- latitude, longitude: center a map or compute proximity.
- place_id, place_link: deep-link or fetch details (e.g., photos, reviews).
- timezone: display local times for business hours; values follow IANA (e.g., Europe/Berlin).
- photos[n].src: show thumbnails; max_size/min_size are pixel dimensions.
2) What is here
Reverse-lookup address and nearby context for coordinates. Useful for “long-press on map” flows or converting GPS into a readable address.
Method: GET
URL: https://zylalabs.com/api/10107/google-maps-api/19306/what-is-here
Required query parameters:
- lat (string): e.g., 48.8719556
- lng (string): e.g., 2.3415407
Example request (parameters shown for clarity):
https://zylalabs.com/api/10107/google-maps-api/19306/what-is-here?lat=48.8719556&lng=2.3415407
Example response (abbreviated fields):
Use address and timezone for UI, place_id for downstream calls, and coordinates for map alignment. Values are standard lat/lng degrees and IANA timezone names.
3) Place Photos
Fetch photos for a specific place using its Place ID. Ideal for showing a photo gallery on a location details page.
Method: GET
URL: https://zylalabs.com/api/10107/google-maps-api/19307/place-photos
Request parameters: none are documented here beyond authentication. Use it to retrieve photos associated with a place.
4) Place Reviews
Retrieve user reviews for a place by Place ID to enrich detail pages with ratings and comments.
Method: GET
URL: https://zylalabs.com/api/10107/google-maps-api/19305/place-reviews
Request parameters: none are documented here beyond authentication.
Copy-paste code: Search and parse results
The snippet below calls the Search endpoint, reads coordinates, and extracts fields needed for a simple “nearby search” UI. Replace YOUR_API_KEY with your key from Zyla.
import requests
API_KEY = "YOUR_API_KEY"
url = "https://zylalabs.com/api/10107/google-maps-api/19301/search"
params = {
"query": "Berlin",
"zoom": "13"
}
headers = {
"Authorization": f"Bearer {API_KEY}"
}
resp = requests.get(url, headers=headers, params=params, timeout=20)
resp.raise_for_status()
payload = resp.json()
if payload.get("status") == "ok":
results = payload.get("data", [])
for item in results:
name = item.get("name")
address = item.get("full_address")
lat = item.get("latitude")
lng = item.get("longitude")
place_id = item.get("place_id")
timezone = item.get("timezone")
photos = item.get("photos", [])
# Print a compact line for your UI or logs
print(f"{name} | {address} | {lat},{lng} | place_id={place_id} | tz={timezone}")
# Use the first photo if available
if photos:
first_photo_url = photos[0].get("src")
print(f"Thumbnail: {first_photo_url}")
else:
raise RuntimeError(f"Search failed: {payload}")
Design notes that will save you time
- Timezones: The API returns IANA names (e.g., Europe/Berlin). Use these directly with your time libraries for localizing business hours and timestamps.
- Coordinates: Latitude and longitude are decimal degrees. For proximity sort, compute great-circle distance or use bounding boxes around the user’s location.
- Thumbnails: The Search response already includes photos with different sizes. Cache the photo URLs on your side to reduce subsequent loads.
- Place IDs: Store place_id from Search or What is here if you plan to fetch photos or reviews later. It’s the stable identifier that links the endpoints.
- Quotas: Zyla uses subscription + quota, not pay-per-call. Monitor usage in your dashboard. The Google Maps API listing offers a 7-day trial or 50 requests to get started.
Putting it together: Nearby search flow
A minimal “search nearby” flow often needs three screens: a search box, a map list, and a place detail. Here’s how to map each step to the endpoints above.
- User types a term: call Search with query and zoom to get candidates with coordinates, timezone, photos, and place_id.
- User taps on the map: call What is here with lat/lng to show a readable address and capture the place_id for deeper details.
- User opens a place: use place_id to load Place Photos and Place Reviews to enrich the details page.
For performance, cache search responses by query+zoom for a short TTL (e.g., a few minutes). When a user drags the map, only re-query when the center changes beyond your threshold.
Endpoint references with examples
Search
GET https://zylalabs.com/api/10107/google-maps-api/19301/search
Example request (from official sample):
https://zylalabs.com/api/10107/google-maps-api/19301/search?query=Berlin&zoom=13
What is here
GET https://zylalabs.com/api/10107/google-maps-api/19306/what-is-here
Required params: lat, lng
Example request:
https://zylalabs.com/api/10107/google-maps-api/19306/what-is-here?lat=48.8719556&lng=2.3415407
Place Photos
GET https://zylalabs.com/api/10107/google-maps-api/19307/place-photos
No request parameters are documented here beyond authentication.
Place Reviews
GET https://zylalabs.com/api/10107/google-maps-api/19305/place-reviews
No request parameters are documented here beyond authentication.
Call the API from AI agents via MCP
Every API on Zyla can also be called from MCP-compatible clients (Claude Code, Cursor, Windsurf, and others). Point your client at the MCP endpoint and provide your key:
- Endpoint: https://mcp.zylalabs.com/mcp?apikey=YOUR_API_KEY
From there, your agent tools can invoke the same Google Maps API endpoints documented above. See the MCP docs for setup in your preferred editor or agent runtime.
Real-world use cases you can ship this week
- Store locator: search “coffee near Mitte” with Search, then show hours and photos on details pages with Place Photos and timezone-aware labels.
- Map tap-to-address: when users long-press on the map, call What is here to show an address card and enable “Save this location”.
- City guide: prefetch Search results for popular queries; use place_id to hydrate detail pages with Place Reviews for better decision-making.
- Booking or delivery radius: filter Search results by distance from the user’s position and display only items within your service radius.
Troubleshooting tips
- Authorization failures: ensure the exact header format Authorization: Bearer YOUR_API_KEY and no extra whitespace.
- Sparse results: adjust your query text (e.g., add a city name) or change zoom to broaden/narrow the search context.
- Time-sensitive UIs: use the timezone field from responses to localize opening hours and user-visible times.
- Network reliability: apply short timeouts and basic retries on transient errors; cache stable fields like place_id and address.
FAQ
How do I authenticate?
Send Authorization: Bearer YOUR_API_KEY on every request.
Is there a free plan?
No. This API runs on subscription + quota. Check the API page for current access options; you can start a 7-day trial or use 50 requests to evaluate.
How do I get a place’s photos or reviews?
Use place_id from Search or What is here, then call Place Photos or Place Reviews respectively.
What units are latitude/longitude?
Decimal degrees. Timezones are IANA strings such as Europe/Paris.
Can I call this from an AI agent?
Yes. Use the MCP endpoint (https://mcp.zylalabs.com/mcp?apikey=YOUR_API_KEY) in an MCP-compatible client and invoke the same endpoints.
Ready to ship your nearby search? Create your account on Zyla API Hub and start the 7-day trial directly on the listing: Start 7-day trial on Google Maps API.