data_idstringrequired
Required Google Maps photo ID. Follow a photo_meta_link from a Google Maps place response or copy the nested photo data_id.
https://api.sandbase.ai/v1/api/google-maps/photo-metadataContributor, place, coordinates, type and date of one Google Maps photo by its data ID.
Your output will appear here
Complete the inputs, then click Run.
Contributor, place, coordinates, type and date of one Google Maps photo by its data ID.
curl -X POST "https://api.sandbase.ai/v1/api/google-maps/photo-metadata" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"data_id": "CIABIhAAQr6KrxiC_knILBjf2RxL"}'
The result is returned in outputs[0].data.
| Name | Type | Required | Description |
|---|---|---|---|
data_id | string | Yes | Required Google Maps photo ID. Follow a photo_meta_link from a Google Maps place response or copy the nested photo data_id. |
gl | string | No | Two-letter country code used to localize results. |
google_domain | string | No | Google domain used for the request. |
hl | string | No | Language code such as en, en-GB, or de. |
timeout | number | No | Optional budget for the entire request in seconds, measured from gateway receipt until the response is ready to send. Includes admission, queueing and settlement. Must be greater t |
Flat price per call. Failed calls are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/google-maps/photo-metadata" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"hl": "en",
"data_id": "CIABIhAAQr6KrxiC_knILBjf2RxL",
"google_domain": "google.com"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
data_idstringrequiredRequired Google Maps photo ID. Follow a photo_meta_link from a Google Maps place response or copy the nested photo data_id.
hlstringLanguage code such as en, en-GB, or de.
Default: "en"
glstringTwo-letter country code used to localize results.
google_domainstringGoogle domain used for the request.
Default: "google.com"
timeoutnumberOptional budget for the entire request in seconds, measured from gateway receipt until the response is ready to send. Includes admission, queueing and settlement. Must be greater than 0 and at most 90. On expiry, the call is not billed and returns 503 request_deadline_exceeded with retryable=true an
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
Google Maps Photo MetadataThis API Google Maps | $0.0001 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/google-maps/photo-metadata with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
$0.0001 per call. Every organization gets 100 free calls per UTC day, shared across eligible SandBase APIs including this one; after that each call is billed at this price from your SandBase balance. There is no subscription.
Required: data_id (string). Optional: hl (string), gl (string), google_domain (string) and timeout (number). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Google Maps Photo Metadata runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Google Maps API access separately.