Only profiles you are authorised to manage
Use the APIs only for listings you own or are authorised to manage; giving others indirect access to your project is not allowed. [4]
Guides · commerce · Verification-gated
Apply for basic access to the Google Business Profile APIs with a Cloud project. You need a Business Profile verified and active for 60+ days with a website listed; until Google approves, the project's quota is 0 QPM, and after approval it is 300 QPM. Calls use OAuth 2.0 with the business.manage scope.
Researched · not yet run liveLast researched 25 October 2026 · Google · provider site
Access is granted to a Google Cloud project, but the application must come from a Google account that is an owner or manager of a verified Business Profile. After approval, your app calls the APIs with OAuth tokens from users who own or manage the profiles being managed.
Quota shown on the Business Profile APIs in the Cloud console tells you the status - 0 QPM pending or rejected, 300 QPM approved.
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
Use a Google Cloud project for the integration and note its project number.
Where: https://console.cloud.google.com/home/dashboard
Confirm the profile is verified, has been active 60+ days, lists the business website, and that your email is an owner or manager.
Where: https://business.google.com/
Open the GBP API contact form, choose "Application for Basic API Access", fill in every field including the project number, and submit it yourself.
Where: https://support.google.com/business/contact/api_default
After approval (300 QPM), enable the My Business APIs you need, such as Account Management and Business Information, in the project.
Where: https://console.cloud.google.com/apis/library
Create an OAuth 2.0 client ID in Credentials and request the business.manage scope from users.
Where: https://console.cloud.google.com/apis/credentials
Plain-English summary, not legal advice. Each card links its source.
Use the APIs only for listings you own or are authorised to manage; giving others indirect access to your project is not allowed. [4]
Using the GoogleLocations endpoint for lead generation or analysis leads to immediate revocation of API access. [4]
You must not automate or trigger review replies, Q&As or listing creation without the user's consent; replying for a client needs their prior authorisation. [4]
Do not pre-fetch, cache, index or store API content; anything stored must be kept no longer than 30 days. [4]
Your product must not suggest a partnership with or endorsement by Google, or copy the Business Profile interface. [4]
| Env var | Secret | Format | What it is |
|---|---|---|---|
GOOGLE_BUSINESS_OAUTH_CLIENT_ID | not secret | 1234567890-abc123.apps.googleusercontent.com | OAuth 2.0 client id used to request the business.manage scope |
GOOGLE_BUSINESS_OAUTH_CLIENT_SECRET | secret | GOCSPX-… | OAuth 2.0 client secret (web server apps) |
Source [1]
The same entry as JSON: /api/v1/entries/google/business-profile-api · requirements /api/v1/requirements/google/business-profile-api · terms /api/v1/terms/google/business-profile-api.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for Google Business Profile APIs (basic access), and how long will it take?"
→ tools/call requirements { "provider_id": "google/business-profile-api" }Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Google is not affiliated with verapli.