Data model
Understand normalized place records, optional fields, nested media, and export formats.
Versioned place records
Place records contain schemaVersion and a place object. The place object includes business identity, address, coordinates, contact fields, ratings, Maps identifiers, and observedAt. Use the published OpenAPI schema for exact field types.
Missing values
A stable field structure does not guarantee that every source value is available. Nullable fields may be null, collections may be empty, and location itself may be null. Do not interpret missing ratings or contact fields as zero or verified absence.
Nested reviews and photos
Place records can include limited reviews and photo metadata. Inspect reviewsState and photosState to distinguish not requested, unavailable, returned, and truncated data. The place schema permits up to 10 nested reviews and 20 photos; these are not complete histories or proof of standalone scraping capability.
Optional enrichment
Email and social collections depend on supported and enabled provider capabilities as well as the source website. Plan entitlement alone does not prove that an enrichment operation is currently available.
Results and exports
Paginated job results include records, next_cursor, and completion information. Eligible Online plans can create CSV, JSON, NDJSON, and Excel exports. Flattened spreadsheet columns and child sheets differ from the nested place JSON; inspect the format before importing it.
Provenance and sample data
Use observedAt to understand when a place was collected, and retain job context when comparing datasets. The homepage CSV sample contains 30 Austin coffee shops transcribed from a Google Maps browser snapshot on September 13, 2026. It includes selected fields and is not an API response. Ratings and review counts may change.