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

# Google My Business Place Actions API

The My Business Place Actions API manages action links - book, order, reserve, menu, appointments - that appear on Google Business Profile listings in Google Search and Maps. It exposes placeActionLinks per location and a placeActionTypeMetadata listing that explains which action types each country and category supports. Use it to drive bookings and orders directly from a Business Profile panel without sending users to a search results page.

## For AI agents

Add and manage action links (book, order, reserve, appointments) on Google Business Profile listings. Use to drive direct conversions from Search and Maps panels.

## Scope

Does not process bookings, take payments, or edit non-action listing fields - use for managing Google Business action link URLs only.

## Capabilities

- Create a place action link such as a booking or ordering URL on a location
- List all action links currently configured on a location
- Update an action link's URL or preferred status
- Delete an obsolete or migrated action link
- Look up which place action types are supported in a region and category
- Mark a specific action link as the preferred entry point for its action type

## Use cases

### Booking Provider Migration

When a brand switches third-party booking providers, every Business Profile location's reserve link must change in lock-step. The placeActionLinks resource supports list, patch, and delete so a workflow can find the old provider's link, replace its URL with the new provider, and mark it preferred - keeping inbound conversion working through the migration window.

Example prompt: List /v1/{parent}/placeActionLinks with placeActionType=RESERVATION, PATCH the URL to the new provider, set isPreferred=true, then DELETE the old link.

### Multi-Location Order-Ahead Roll-Out

Quick-service brands launching online ordering need an order link on every storefront's Business Profile. The Place Actions API accepts a per-location create with placeActionType=ONLINE_APPOINTMENT or FOOD_ORDERING, so a fan-out across the location list adds the new conversion point in minutes rather than per-location UI clicks.

Example prompt: Iterate over locations under accounts/{account} and POST /v1/{parent}/placeActionLinks with placeActionType=FOOD_ORDERING_DELIVERY and the order URL.

### Region-Aware Action Coverage

Place action types are not uniformly supported across countries and categories. The placeActionTypeMetadata endpoint returns which types are valid given a regionCode and category, letting a workflow filter out unsupported actions before attempting to create them and avoiding 400 errors on PATCH.

Example prompt: GET /v1/placeActionTypeMetadata with regionCode and languageCode, build the supported set, and only create links whose placeActionType is in that set.

### AI Agent Conversion Optimiser

An AI agent reachable through Jentic compares conversion data per location, tests new action link URLs, and rotates the preferred booking partner. Jentic isolates OAuth credentials and exposes the right Place Actions operation per intent so the agent never reads the discovery document or holds Google client secrets.

Example prompt: Search Jentic for 'add a booking link to a Google Business listing', load placeActionLinks.create, and execute with placeActionType=RESERVATION and the test URL.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/placeActionTypeMetadata | List supported action types and required fields |
| GET | /v1/{parent}/placeActionLinks | List action links on a location |
| POST | /v1/{parent}/placeActionLinks | Create an action link on a location |
| PATCH | /v1/{name} | Update an action link |
| DELETE | /v1/{name} | Delete an action link |

## Key resources

- **placeActionLinks** — Action links such as booking, ordering, and appointments configured per location
- **placeActionTypeMetadata** — Catalogue of supported action types per region and category

## Why Jentic

- **Setup:** Wiring the My Business Place Actions API by hand means setting up Google OAuth 2.0 for Business Profile access, refreshing short-lived bearer tokens, and tracking the v1 place-action surface yourself against the mybusinessplaceactions.googleapis.com host. Through Jentic you install once, import the My Business Place Actions API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** This API puts the location and action-link name in the URL path (/v1/{parent}/placeActionLinks and /v1/{name}), so a rule can pin your agent to one Business Profile location: it can read place-action metadata and list and create action links there and nothing else. You choose the operations it may call, so destructive ones like deleting an action link are not included unless you add them.
- **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 'add a booking link to a Google Business listing' or 'list place action links', and Jentic returns the matching Place Actions 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 parent location whose action links this API manages
- **Google My Business API (v4)** — Older monolithic API with overlapping but coarser action link support
- **My Business Verifications API** — Verifies new locations before action links can appear publicly
- **Google Places API** — Reads action links and place details for end-user discovery

## FAQ

### What authentication does the My Business Place Actions API use?

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

### Can I add a Reserve with Google link via this API?

Yes. POST /v1/{parent}/placeActionLinks with placeActionType=RESERVATION and the URL of your booking provider's deep link. Mark isPreferred=true if it should be the default reservation link on the listing.

### What are the rate limits for the My Business Place Actions API?

Default quota is 0 QPM until Business Profile API access is granted. Once approved Google sets per-minute and per-day quotas; bulk action link sweeps should be paced and back off on 429 responses.

### How do I update an action link through Jentic?

Search Jentic for 'update Google Business action link', load placeActionLinks.patch, and execute it with the new URL and updateMask=uri. Jentic handles the OAuth refresh in the background.

### Why does creating an action link return INVALID_ARGUMENT for some categories?

Place action types are restricted by region and category. Call GET /v1/placeActionTypeMetadata with the location's regionCode and languageCode to see which types are valid for the location before creating the link.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API puts the location and action-link name in the URL path (/v1/{parent}/placeActionLinks and /v1/{name}), so you can pin the agent to a single Business Profile location. You choose the exact operations it may call, so you can allow it to read place-action metadata and list and create action links while withholding destructive ones like deleting an action link. Because the OAuth credential is injected only at execution time and never enters the agent's context, the agent can act only within the location and operations you have granted.