Google My Business Lodging API

Name: My Business Lodging API
Brand: My Business Lodging API
Availability: InStock

✓ Official Vendor SpecMarketingContent Managementoauth23 EndpointsREST

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with My Business Lodging API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

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.

Time to first call

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.

Google My Business Lodging API

Connect the My Business Lodging API to your agent

Capabilities

Start building with My Business Lodging API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs