Google My Business Lodging API
Browse all Google APIs46
AI ReadinessFoundational (D)46/100
Official vendor OpenAPI document · agent-readyMarketingContent Managementoauth23 EndpointsREST
For Agents
Manage lodging-specific attributes (amenities, accessibility, family features) on Google Business Profile hotel listings. Use to keep travel listings accurate.
Use for: Update the pool and gym amenities on a hotel listing, Mark a property as wheelchair accessible across all relevant rooms, Compare my lodging data against Google's auto-detected fields, Get the current lodging amenity profile for a hotel location
Not supported: Does not handle bookings, room rates, reviews, or general listing fields - use for lodging amenity and accessibility metadata only.
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.
Install Jentic One Beta
Connect the My Business Lodging API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the My Business Lodging API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fmybusinesslodging" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fmybusinesslodging" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with My Business Lodging API.
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
Patterns agents use My Business Lodging API for, with concrete tasks.
★ 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.
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.
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.
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.
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
3 endpoints — the my business lodging api manages lodging-specific attributes for hotels, b&bs, and other accommodations on google business profile.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
My Business Lodging API
- Foundational (D)46/100
69
Foundational Compliance56
Developer Experience & Jentic Compatibility24
AI-Readiness & Agent Experience94
Agent Usability100
Security33
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
69
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B+Signals: 4
77%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
24
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
96%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
33
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
33%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using My Business Lodging API through Jentic.
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.
GET STARTED