google-maps/
place-details

The Google Maps Place Details API collects details for known public Google Maps URLs, returning normalized place identity, category, address, contact, rating, review-count, website, and geographic fields.

Google Maps Place Details API

Known Maps URLs
Place details
Normalized locations
0.15 credits / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Google Maps Place Details

Public Google Maps place pages can expose names, categories, descriptions, addresses, contact details, ratings, review counts, websites, and geographic context. Normalized records make those visible fields easier to join with location inventories, venue research, directory enrichment, and point-in-time monitoring.

Google Maps Place Details API Features

  • Batch URL detail collectionSubmit one or more known Google Maps URLs and let each non-empty input become one provider detail row, capped internally at the number of submitted URLs.
  • Stable place recordsThe Google Maps Place Details API returns identity, source URL, name, description, category, address, phone, website, rating, and review count through the PlaceItem schema.
  • Structured geographic contextKeep available location name, city, region, country, latitude, and longitude together instead of parsing them from presentation text.
  • Result-based billingEstimate at 0.15 credits per submitted URL, then settle at 0.15 credits for each successfully returned standard place record; empty results have no charge.

Google Maps Place Details API Parameters

ParametersRequiredDescription
urlsRequiredRequired non-empty array of references whose parser yields a hostname. The runtime accepts google.com, goo.gl, and their subdomains by hostname; it accepts any scheme with an authority component and protocol-relative references, and does not require a particular path pattern.

How to Use the Google Maps Place Details API

Submit known Google Maps URLs to the Google Maps Place Details API, track the asynchronous task, and read every saved PlaceItem through the standard cursor result envelope.

  1. Prepare one or more references whose parsed hostname is google.com, goo.gl, or a subdomain of either accepted host.
  2. POST urls to /v1/google-maps/place-details and save the returned task_id.
  3. Poll /v1/tasks/{task_id} until the task succeeds or fails.
  4. Read data.results.items and follow next_cursor while has_more is true; the submit request itself has no results_limit field.
curl -X POST "https://api.socq.ai/v1/google-maps/place-details" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.google.com/maps/place/Coffee%20Project%20New%20York%20%7C%20East%20Village/data=!4m7!3m6!1s0x89c2599b5a24d7fd:0x9e354f6cf514b9fc!8m2!3d40.7270884!4d-73.9893820!16s%2Fg%2F11c3svpqld!19sChIJ_dckWptZwokR_LkU9WxPNZ4?authuser=0&hl=en&rclk=1"]}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Google Maps Place Details API Use Cases

  • Location directory enrichment: Add normalized category, address, phone, website, rating, review-count, and coordinate fields to known place URLs.
  • Venue and branch audits: Revisit a controlled URL list with the Google Maps Place Details API to compare visible identity, contact, rating, and geographic values at defined collection times.
  • Place-record reconciliation: Use returned IDs, source URLs, names, addresses, and coordinates to match public places with internal location records.

Google Maps Place Details API Pro Tips

  • Submit complete absolute Maps URLs so the parser can resolve an accepted hostname; bare hostnames without a scheme do not produce a hostname in the runtime parser.
  • Do not add Place IDs, Google API keys, field masks, or results_limit because they are not fields in this SocQ request contract.
  • Treat each submitted URL as a detail candidate, not a guaranteed result; unavailable or unusable source rows can leave fewer items than URLs.
  • Preserve nullable phone, website, rating, review count, description, publication time, and location members rather than inventing fallback values.
  • Continue through next_cursor whenever has_more is true because pagination applies when reading saved task results, even though the provider cap comes from the URL count.

Beyond the Google Maps Place Details API, use these APIs when you need a different type of public Google Maps data.

Explore other platforms

Combine Google Maps data with public data from other supported social platforms.

Google Maps Place Details API — FAQ

Google Maps Place Details API turns known public Google Maps URLs into normalized PlaceItem records. It returns available identity, category, contact, rating, review-count, address, website, and location fields.

Submit references whose parsed hostname is google.com, goo.gl, or a subdomain of either host. Any scheme is accepted when an authority and hostname are present, protocol-relative references are also accepted, and no specific /maps/place path is required.

No. The request accepts known public Google Maps URLs through SocQ and does not accept an official Place ID, Google API key, OAuth credential, or field mask.

No. The provider input contains one detail row per non-empty URL and an internal cap equal to that row count; results_limit is not a public request field.

A source URL can be unavailable, return an error row, or fail to produce a usable normalized place. Other submitted URLs continue independently.

Poll GET /v1/tasks/{task_id}, read data.results.items after success, and request the next page with next_cursor while has_more is true.

The estimate is 0.15 SocQ credits per non-empty submitted URL. Final billing is 0.15 credits per successfully returned standard place record, and an empty result set costs zero credits.