Look up a Google Business Profile for onboarding prefill

Server-side proxy for Google Places Details (New). Exists so the credential with Details access never reaches a browser: the client-side Autocomplete widget holds a separate, referrer-restricted key that can only produce predictions.

Google's response shape is mapped to this app's own shapes here, so no Google type reaches the client; addressComponents become country/state/city/postalCode, regularOpeningHours.periods become the same DayWindow array WeekHoursEditor already edits.

Always 200, even when nothing is found. The wizard treats "no data" as "stay in manual entry", never as an error, so a miss and a Google-side failure collapse to the same {found:false} rather than becoming a dead end mid-onboarding.

Field selection here is a BILLING decision, not a performance one: Google charges Place Details at the tier of the MOST EXPENSIVE field requested. regularOpeningHours and businessStatus are Enterprise-tier and opening hours are the point of the feature, so this call is already billed at Enterprise, which is what makes nationalPhoneNumber (also Enterprise) and primaryType (Pro, below it) free at the margin. Check the per-field tier table in Google's Place Details docs before adding to the mask; one field a tier up raises the price of every lookup.

The phone number used to be excluded here on the grounds that step 3 showed no phone field, and nothing should be written that the operator cannot see and correct. That reasoning stands; the premise changed: step 3 now shows address and phone, so both are prefilled and both are correctable. websiteUri (Pro tier, also free at the margin) was added 2026-08-19; still not extracted: rating, reviews, photos or editorialSummary/description, all Enterprise+Atmosphere, a tier above what this call already pays. Reviews specifically are strictly worse here than the OAuth Google Business Profile connection (docs/google-business-profile.md) already gets: up to 5 Google-picked reviews with no reply capability, versus that connection's full history and reply-to-review. Not a fit for a call that fires on every signup regardless of whether the business ever uses reviews.

Response BodyCopy Anchor Link

curl -X POST "https://example.com/api/places/details" \  -H "Content-Type: application/json" \  -d '{    "placeId": "string"  }'

{  "found": true,  "name": "string",  "address": "string",  "country": "string",  "state": "string",  "city": "string",  "postalCode": "string",  "lat": 0,  "lng": 0,  "businessStatus": "string",  "phone": "string",  "primaryType": "string",  "website": "string",  "hours": [    {      "dayOfWeek": 0,      "startTime": "string",      "endTime": "string"    }  ]}