Google My Business Verifications API
Browse all Google APIs✓ Official Vendor SpecIdentity AuthIdentity Verificationoauth25 EndpointsREST
For Agents
Run the Google Business Profile location verification flow — fetch options, start verification, submit codes, and check Voice of Merchant state.
Use for: Get the available verification options for a new location, Start a postcard verification on a location, Submit the verification code received on the postcard, Check whether a location is fully verified
Not supported: Does not edit listing content, manage admins, or send marketing messages — use for Google Business Profile location ownership verification only.
The My Business Verifications API runs the ownership verification flow for Google Business Profile locations. It exposes endpoints to fetch the verification options available to a location (postcard, phone, email, video), start a verification, complete it with a code, list past attempts, and read the Voice of Merchant state that gates listing visibility. Pair it with the Business Information API after verification succeeds to start managing listing content.
Install Jentic One Beta
Connect the My Business Verifications API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the My Business Verifications 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Verifications API.
Fetch the verification options available for a specific location
Start a verification using postcard, phone, email, or video method
Complete an in-progress verification by submitting the received code
List historical verification attempts on a location
Read the Voice of Merchant state to confirm a listing is fully verified
Detect when a verification has expired and a new one is required
Use Cases
Patterns agents use My Business Verifications API for, with concrete tasks.
★ Bulk Onboarding for New Locations
Franchise and multi-brand operators onboard many new locations in waves. The Verifications API lets a workflow create the location via Business Information, fetch verification options, kick off the operator-preferred method, and track the Voice of Merchant state until each listing goes live — replacing manual verification queues per location.
POST /v1/{location}:fetchVerificationOptions, choose the preferred method, POST /v1/{parent}/verifications, then poll /v1/{name}/VoiceOfMerchantState until verified.
Postcard Code Reconciliation
When a postcard arrives with a verification code, the operator must complete the right pending verification. The verifications:complete endpoint accepts the code and resource name, closing the loop programmatically — useful for back-office operations that scan postcards to a queue rather than typing codes into a UI.
POST /v1/{name}:complete with the verification code, then GET the verification to confirm state=COMPLETED.
Voice of Merchant Health Check
Verification can lapse if Google detects suspicious activity or if location data drifts. Periodically reading the VoiceOfMerchantState surfaces locations whose visibility is suspended, letting an operator team trigger a re-verification before the listing's ranking suffers.
GET /v1/{name}/VoiceOfMerchantState across all locations and flag any whose hasVoiceOfMerchant=false for re-verification.
AI Agent Verification Concierge
An AI agent reachable through Jentic onboards new locations end to end: it creates the location via Business Information, fetches verification options, kicks off the chosen method, and watches for Voice of Merchant. Jentic isolates the OAuth credentials and returns the right Verifications operation per intent.
Search Jentic for 'start a Google Business verification', load locations.verifications.create, and execute with the chosen method and contact details.
Key Endpoints
5 endpoints — the my business verifications api runs the ownership verification flow for google business profile locations.
METHOD
PATH
DESCRIPTION
POST
/v1/{location}:fetchVerificationOptions
List verification methods available for a location
GET
/v1/{name}/VoiceOfMerchantState
Get the Voice of Merchant verification state
POST
/v1/{name}:complete
Complete a verification by submitting its code
POST
/v1/{name}:verify
Start a verification on a location
GET
/v1/{parent}/verifications
List verification attempts on a location
POST
/v1/{location}:fetchVerificationOptions
List verification methods available for a location
GET
/v1/{name}/VoiceOfMerchantState
Get the Voice of Merchant verification state
POST
/v1/{name}:complete
Complete a verification by submitting its code
POST
/v1/{name}:verify
Start a verification on a location
GET
/v1/{parent}/verifications
List verification attempts on a location
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OAuth 2.0 refresh tokens are stored encrypted in the Jentic vault. The agent receives scoped, short-lived access tokens — Google client secrets never enter the agent context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'start a Google Business verification') and Jentic returns the matching Verifications operation with its input schema.
Time to first call
Direct integration: 2-4 days for OAuth, method selection logic, and Voice of Merchant polling. Through Jentic: under an hour for the API surface — verification still gated by postal or call latency.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using My Business Verifications API through Jentic.
What authentication does the My Business Verifications API use?
OAuth 2.0 with the https://www.googleapis.com/auth/business.manage scope. The caller must be an admin on the parent Business Profile account. Jentic stores OAuth refresh tokens in MAXsystem and exposes only scoped short-lived access tokens to the agent.
Which verification methods does the API support?
fetchVerificationOptions returns the methods available for the location, which can include POSTCARD, PHONE_CALL, EMAIL, VIDEO, and AUDIT depending on category and country. Service-area businesses often only see VIDEO.
What are the rate limits for the My Business Verifications API?
Default quota is 0 QPM until Business Profile API access is approved. Once approved Google sets per-minute and per-day quotas; verification flows are not high-throughput, so the practical limit is the postal or call latency of each method.
How do I start a verification through Jentic?
Search Jentic for 'start a Google Business verification', load locations.verifications.create, and execute with the chosen verificationMethod and the languageCode. Jentic handles OAuth refresh in the background.
How do I tell that a location is fully verified?
GET /v1/{name}/VoiceOfMerchantState. A location is considered fully verified when hasVoiceOfMerchant=true; otherwise the response lists complianceReasons explaining what is blocking visibility.
GET STARTED