canonical: https://jentic.com/apis/googleapis.com/mybusinesslodging

# Google My Business Lodging API

The My Business Lodging API manages lodging-specific attributes for hotels, B&Bs, and other accommodations on Google Business Profile. It exposes a Lodging resource per location that captures amenities, accessibility features, family options, business centre availability, and Google-updated lodging signals so listings appear correctly in Google Search and Google Travel surfaces. Use it together with Business Information for general listing data and Verifications for ownership checks.

## For AI agents

Manage lodging-specific attributes (amenities, accessibility, family features) on Google Business Profile hotel listings. Use to keep travel listings accurate.

## Scope

Does not handle bookings, room rates, reviews, or general listing fields - use for lodging amenity and accessibility metadata only.

## Capabilities

- Read the full lodging amenity profile for a verified hotel location
- Update amenities such as pool, gym, parking, and Wi-Fi for a property
- Set accessibility and family-friendly attributes on a lodging listing
- Compare local edits against Google's auto-updated lodging signals
- Apply field masks to patch only the lodging sections that changed
- Surface mismatches between operator data and Google's view of the property

## Use cases

### Hotel Amenity Sync

Hotel groups maintain amenity data in a property management system and need it reflected on Google Search and Google Travel. The Lodging API accepts a structured amenity payload per location, so a sync job can patch updated amenities - pool hours, parking type, Wi-Fi tier - straight from the PMS without manual edits in the Business Profile UI.

Example prompt: PATCH /v1/{name} with the lodging body containing updated amenities and an updateMask listing only the changed paths.

### Google-Updated Drift Detection

Google sometimes auto-fills lodging signals from third-party sources. Operators use getGoogleUpdated to compare Google's view against the operator's, then patch the canonical record where they disagree. This keeps the operator's data authoritative on properties' Google profiles.

Example prompt: GET /v1/{name}:getGoogleUpdated, diff the response against the operator record, and PATCH any mismatches with the corrected values.

### Accessibility Compliance Roll-out

Brands rolling out accessibility commitments across a portfolio need every hotel listing to expose accurate accessibility attributes. The Lodging API has a dedicated accessibility section that can be patched per property in bulk, ensuring the listing matches the on-site reality before audits.

Example prompt: For each hotel location, PATCH /v1/{name} with accessibility fields set and updateMask=accessibility, then GET to confirm persistence.

### AI Agent Lodging Curator

An AI agent reachable through Jentic ingests changes from a hotel's CMS and updates the Lodging record on Google. Jentic isolates the OAuth credentials and returns the right Lodging operation per intent, removing the need for the agent to know the discovery document or manage refresh tokens.

Example prompt: Search Jentic for 'update Google Business hotel amenities', load locations.lodging.patch, and execute it with the new amenity payload and an updateMask.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/{name} | Get the lodging record for a location |
| PATCH | /v1/{name} | Update the lodging record |
| GET | /v1/{name}:getGoogleUpdated | Get Google's auto-updated lodging fields for comparison |

## Key resources

- **lodging** — Lodging-specific attribute record attached to a Business Profile location

## Why Jentic

- **Setup:** Wiring the My Business Lodging API by hand means setting up Google OAuth 2.0 for Business Profile access, minting short-lived bearer tokens, and tracking the v1 lodging surface yourself against the mybusinesslodging.googleapis.com host. Through Jentic you install once, import the My Business Lodging API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** The Lodging API puts the location name in the URL path (/v1/{name}), so a rule can pin your agent to one lodging location: it can read amenity metadata and the Google-updated view there and nothing else. You choose the operations it may call, so patching lodging metadata is not included unless you add it.
- **Credential handling:** Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'update Google Business hotel amenities' or 'read lodging accessibility metadata', and Jentic returns the matching Lodging operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **My Business Business Information API** — Edits the general listing content (address, hours, categories) for the same hotel location
- **My Business Verifications API** — Verifies ownership of new hotel locations before lodging fields can be edited
- **Google My Business API (v4)** — Legacy monolithic API with overlapping but coarser location editing surfaces
- **Google Places API** — Read-only place data including hotel details for end-user discovery

## FAQ

### What authentication does the My Business Lodging API use?

OAuth 2.0 with the https://www.googleapis.com/auth/business.manage scope. The user must be an admin of the parent Business Profile account. Through Jentic the OAuth refresh token is stored encrypted in your Jentic One instance and the agent only sees short-lived access tokens.

### Can I update hotel amenities for many properties at once?

There is no batch endpoint. A workflow lists all hotel locations under the account and PATCHes each /v1/{name} with the new lodging body. Use updateMask to limit the fields updated and reduce 429 risk.

### What are the rate limits for the My Business Lodging API?

Default quota is 0 QPM until you request Business Profile API access from Google. Once approved Google sets per-minute and per-day quotas; bulk amenity sweeps should pace requests and retry on 429 with exponential backoff.

### How do I update hotel amenities through Jentic?

Search Jentic for 'update Google Business hotel amenities', load locations.lodging.patch, and execute it with the lodging body and an updateMask listing only the changed amenity paths. Jentic handles OAuth refresh in the background.

### What does getGoogleUpdated do?

GET /v1/{name}:getGoogleUpdated returns the lodging fields Google has auto-detected from third-party sources, plus a diff mask versus the operator's data. Use it to detect drift and re-assert authoritative values via PATCH.

### Can I limit what my agent is allowed to do with the My Business Lodging API?

Yes. Because you self-host Jentic One, your own rules decide which lodging operations and OAuth credential the agent may use. Since this API carries the location name in the URL path (/v1/{name}), you can pin the agent to a single lodging location and grant only read access, letting it fetch the amenity profile with GET /v1/{name} and compare Google's auto-updated view via getGoogleUpdated. The PATCH operation that writes lodging metadata stays off limits unless you explicitly add it to what the agent may call.