Google Maps Photos API
Retrieve public photos and photo categories for a Google Maps location.
Collect public image URLs and available photo categories for listing QA, location research, or media review.
{
"request_id": "example_google_maps_photos",
"tool": "google_maps_photos",
"output": {
"data": {
"categories": [],
"photos": [
{
"image": "https://example.com/photo.jpg",
"thumbnail": "https://example.com/photo-thumb.jpg"
}
]
},
"data_id": "example_data_id"
},
"usage": {
"price_usd": "0.003125",
"quota": 1563
}
}Google Maps Photos API Pricing
Current pricing from the APINEED catalog. Failed requests are refunded; server usage records remain authoritative.
Quick Start
Invoke Google Maps Photos with one APINEED key and a JSON request body.
Use your APINEED API key
Reuse the same APINEED API key that your application already uses for LLM, image, and video APIs. Keep it server-side.
Create API keyexport API_NEED_API_KEY=sk-apineed-v1-...Send the request
POST the same input shown in the Playground to /v1/tools/google_maps_photos/invoke.
curl 'https://apineed.com/v1/tools/google_maps_photos/invoke' \
-H "Authorization: Bearer $API_NEED_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"data_id": "example_data_id",
"language": "en"
}'Read the response
Use output.data.photos for the result and usage.price_usd for the settled request price.
const data = response.output.data.photos;Endpoint
This endpoint uses bearer-token authentication and returns a synchronous normalized JSON response.
/v1/tools/google_maps_photos/invoke- Authorization
- Bearer $API_NEED_API_KEY
- Content-Type
- application/json
- Billing
- $0.003125 per request on successful invocation
- Response
- request_id, tool, output, usage
Google Maps Photos API Parameters
data_id is required and comes from Google Maps Search. Pagination or filtering fields are optional.
| Name | Type | Requirement | Values | Description |
|---|---|---|---|---|
data_id | string | Required | 1–2048 characters | Google Maps location data ID returned by Maps Search. |
category_id | string | Optional | 1–2048 characters | Optional category ID returned by a previous photos response. |
language | string | Optional | Pattern: ^[A-Za-z]{2}$ | Optional two-letter result language. Defaults upstream to en. |
next_page_token | string | Optional | 1–8192 characters | Optional token returned by a previous photos response. |
Google Maps Photos API Introduction
A practical guide to the request, response, billing, and application use cases.
Google Maps Photos API
Collect public image URLs and available photo categories for listing QA, location research, or media review.
Listing QA
Review public images associated with a location.
Visual research
Collect photo URLs for approved research and moderation workflows.
Request contract
Send a JSON object to /v1/tools/google_maps_photos/invoke. Use the required fields, supported optional parameters, and bounds listed above. Undocumented parameters are not guaranteed to be supported.
Response and usage
Read the tool result from output.data.photos and the settled charge from usage.price_usd. Keep request_id for troubleshooting. Preserve optional response fields rather than assuming they are always present.
Common Questions
Practical answers about authentication, parameters, pricing, and integration.
What does Google Maps Photos API do?
Collect public image URLs and available photo categories for listing QA, location research, or media review.
How do I authenticate?
Send a POST request to /v1/tools/google_maps_photos/invoke with your APINEED API key in the Authorization: Bearer header. The same key can be used for model APIs. Keep the key on your server, not in browser code.
Can I try this API without entering an API key?
Yes. The Playground uses your signed-in APINEED account and shared balance. Sign in to send a request, or add funds if your balance is insufficient.
Which input fields are required?
Required fields: data_id. Check the parameter table for types, allowed values, and limits.
Can I omit optional parameters?
Yes. Optional fields: category_id, language, next_page_token. Omitted fields are not sent. Explicit false and 0 values are preserved; use the defaults and limits documented in the parameter table.
How much does a request cost?
The current catalog price is $0.003125 per request. The final charge is recorded in usage.price_usd and your account usage logs. Failed requests are refunded.
How should I read the response?
A successful invocation returns request_id, tool, output, and usage. Read the result from output, preserve request_id for troubleshooting, and inspect usage for the settled charge. The Playground shows the returned JSON without changing it.
