Google My Business Notifications API
Browse all Google APIs35
AI ReadinessNon-Ready (F)35/100
Official vendor OpenAPI document · agent-readyCommunicationsPush Notificationsoauth22 EndpointsREST
For Agents
Configure which Google Business Profile events get pushed to a Cloud Pub/Sub topic. Use to drive event-based workflows for reviews, questions, and listing changes.
Use for: Subscribe new review events to my Cloud Pub/Sub topic, Stop sending new question notifications to the old topic, Get the current notification configuration for the account, Switch the Pub/Sub topic to a new project
Not supported: Does not deliver event payloads, send emails, or push mobile notifications - use only to configure which Business Profile events publish to a Cloud Pub/Sub topic.
The My Business Notifications API configures Pub/Sub-based notification settings for Google Business Profile accounts. It exposes a single notificationSetting resource per account that controls which Business Profile events (new reviews, questions, status changes) are pushed to a Cloud Pub/Sub topic. Pair it with the Q&A and v4 reviews endpoints to build event-driven Business Profile workflows instead of polling.
Install Jentic One Beta
Connect the My Business Notifications API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the My Business Notifications 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%2Fmybusinessnotifications" | 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%2Fmybusinessnotifications" | 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 Notifications API.
Read the current notification setting for a Business Profile account
Subscribe an account's events to a Cloud Pub/Sub topic
Select which event types - reviews, questions, listing changes - to receive
Update the target Pub/Sub topic when migrating environments
Disable notifications by clearing the Pub/Sub topic on the setting
Verify which events the current setting is configured to deliver
Use Cases
Patterns agents use My Business Notifications API for, with concrete tasks.
★ Event-Driven Review Reply
Instead of polling every location for new reviews, teams subscribe to Business Profile review events on a Pub/Sub topic. When a new review arrives, a worker picks up the event and triggers reply automation against the v4 reviews endpoint, cutting average response time without burning quota on polling.
PATCH /v1/{name} with pubsubTopic set to projects/{project}/topics/{topic} and notificationTypes including NEW_REVIEW, then verify with a GET.
Real-Time Q&A Monitoring
Customer questions on Business Profile listings need quick answers. Subscribing the account's notification setting to NEW_QUESTION and NEW_ANSWER events on a Pub/Sub topic streams every question into a queue, enabling support to triage and reply through the My Business Q&A API within minutes.
PATCH /v1/{name} with notificationTypes set to NEW_QUESTION, NEW_ANSWER and the support-team Pub/Sub topic, then confirm via GET.
Environment Migration
When teams move Pub/Sub from one Google Cloud project to another, the Business Profile notification setting must be repointed without dropping events. Update the notificationSetting's pubsubTopic to the new fully qualified topic and Google starts publishing to the new project with no other changes required.
PATCH /v1/{name} with pubsubTopic set to the new project topic and updateMask=pubsubTopic, then verify message delivery in the new project.
AI Agent Listing Watcher
An AI agent connected through Jentic owns a Business Profile inbox: every new review, question, or listing change lands in a Pub/Sub topic, the agent enriches the event, and routes it to the right responder. Jentic isolates the OAuth credentials so the agent never sees Google client secrets while still being able to reconfigure the notification setting on demand.
Search Jentic for 'configure Google Business Pub/Sub notifications', load accounts.notificationSetting.update, and execute with the desired notificationTypes and pubsubTopic.
Key Endpoints
2 endpoints — the my business notifications api configures pub/sub-based notification settings for google business profile accounts.
METHOD
PATH
DESCRIPTION
GET
/v1/{name}
Get the notification setting for an account
PATCH
/v1/{name}
Update the Pub/Sub topic and event types
GET
/v1/{name}
Get the notification setting for an account
PATCH
/v1/{name}
Update the Pub/Sub topic and event types
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 Notifications API
- Non-Ready (F)35/100
73
Foundational Compliance56
Developer Experience & Jentic Compatibility13
AI-Readiness & Agent Experience94
Agent Usability100
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
91%
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.
13
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
53%
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).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
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 Notifications API by hand means setting up Google OAuth 2.0 for Business Profile access, minting short-lived bearer tokens, and wiring the Cloud Pub/Sub notification setting yourself against the mybusinessnotifications.googleapis.com host. Through Jentic you install once, import the My Business Notifications API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
This API puts the account notification-setting name in the URL path (/v1/{name}), so a rule can pin your agent to one Business Profile account's notification setting: it can read that setting and nothing else. You choose the operations it may call, so patching which events publish to Pub/Sub 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 'subscribe to Google Business review events' or 'read notification settings', and Jentic returns the matching Notifications 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 Notifications API through Jentic.
What authentication does the My Business Notifications 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 and the service account behind the Pub/Sub topic must grant publish rights to mybusiness-api-pubsub@system.gserviceaccount.com. Jentic stores OAuth tokens in your Jentic One instance.
Which event types can I subscribe to?
The notificationSetting accepts notificationTypes such as NEW_REVIEW, UPDATED_REVIEW, NEW_QUESTION, NEW_ANSWER, and GOOGLE_UPDATE. Pick the subset relevant to your workflow to avoid noisy event traffic.
What are the rate limits for the My Business Notifications API?
Default quota is 0 QPM until Business Profile API access is approved. Once approved, the API itself is rarely rate-limited because the resource is read or patched infrequently; the bottleneck is downstream consumption of the Pub/Sub topic.
How do I switch the Pub/Sub topic through Jentic?
Search Jentic for 'change Google Business notification topic', load accounts.notificationSetting.update, and execute it with the new pubsubTopic and updateMask=pubsubTopic. Jentic handles OAuth refresh in the background.
Does this API deliver the actual review or question content?
Notifications carry the resource name and event type, not the full payload. After receiving an event, fetch the resource via the v4 Google My Business reviews endpoint or the My Business Q&A API to retrieve the body.
Can I limit what my agent is allowed to do with the My Business Notifications API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API keeps the notification-setting name in the URL path (/v1/{name}), so a rule can pin the agent to a single Business Profile account's setting. You can allow only the GET so the agent reads the current notification configuration and nothing else, keeping the PATCH that changes which events publish to Pub/Sub off the table unless you grant it. Your Google OAuth credential stays in your instance and is injected at call time, so the agent never sees the client secret.
GET STARTED