Google Business Profile API Access: Why It Is Not Just an “Enable API” Click
A SaaS team building multi-location review and post management tooling assumes that once the Google Business Profile APIs are enabled in Google Cloud Console, the integration is ready to call. The first request comes back with a quota error. Nothing is broken — the project has not been approved yet, and approval for this API does not happen automatically.
Google Business Profile API access sits behind a manual review gate that is separate from simply enabling the API. Here is what that gate actually checks, why it trips up otherwise-solid integrations, and where it connects to the Google OAuth verification work already covered on this site.
What Access to the Google Business Profile API Actually Requires
Google’s own prerequisites page lists a specific set of conditions before an access request is even worth submitting:
60+ Day Verified Profile
The Business Profile being connected — the applicant’s own listing or one they manage for a client — must already be verified and active for at least 60 days before applying.
A Live Business Website
The Business Profile must list a real website for the business. An incomplete listing without a website is treated as unready for review.
Google Cloud Project
A project created in Google Cloud Console, with its Project Number recorded, is required before the access request can be submitted.
Organization Account
Google directs applicants to set up an Organization account through the Business Profile help center as part of the prerequisites.
Owner/Manager Email
The request must be submitted using an email address that is already listed as an owner or manager on the Business Profile being connected.
OAuth Consent Screen + Scope
The integration authenticates with the business.manage OAuth scope, which means the same OAuth consent screen configuration used across other Google API integrations applies here too.
Why This Trips Up Otherwise-Ready Integrations
Enabling the Business Profile APIs in Cloud Console does not grant usable quota. Google documents the check directly:
That single line explains most of the confusion developers run into: the API looks enabled, the credentials look correct, and every call still fails on quota. A few places this specifically stalls integrations:
Application Submitted Through the Wrong Email
Google explicitly requires the request to come from an email already listed as owner/manager on the GBP — a developer or agency using their own separate email is a common mismatch.
Profile Not Actually 60+ Days Verified
Recently verified or recently claimed listings do not meet the eligibility bar yet, even if every other technical piece is ready.
Incomplete Business Profile
Google recommends the profile be “fully complete and kept up-to-date” before applying — a thin or outdated listing works against a smooth review.
OAuth Consent Screen Not Ready
Because the API sits behind the business.manage scope, an unfinished or unverified OAuth consent screen creates a second blocker on top of the GBP access request itself.
Quota Before and After Approval
| State | Quota | What It Means |
|---|---|---|
| Not yet approved | 0 QPM | Every Business Profile API call fails on quota, regardless of valid credentials |
| Approved | 300 QPM | Project has cleared the manual access review and can call the APIs |
Checking this quota value in Google Cloud Console is the documented way to confirm whether an application has actually been approved, rather than assuming approval from an enabled-API status alone.
The Path From Zero Access to an Approved Integration
Confirm eligibility first
Verify the 60-day-plus verification status and the presence of a real business website on the profile before anything else — applying too early is a common, avoidable rejection.
Set up the Cloud project and Organization account
A Google Cloud project with a recorded Project Number, plus the Organization account step, both need to be in place before the request form is submitted.
Configure OAuth credentials and the consent screen
The business.manage scope and a properly configured OAuth consent screen need to be ready in parallel with the access request, not after it.
Submit the Basic API Access request
Google’s GBP API contact form asks for the Project Number and business details, from the correct owner/manager email — the specifics of a strong submission are where most rejected requests actually fail.
Confirm approval through quota, then enable the APIs
Once quota shows 300 QPM instead of 0 QPM, the Business Profile APIs can be enabled for the project and the OAuth flow can go live.
Where GBP API Requests Get Rejected or Stall
- Applying before the 60-day verification window is met — Google states this as a hard prerequisite, not a guideline.
- Submitting from an email not listed as owner or manager on the target Business Profile.
- No website listed on the profile, which Google treats as a missing prerequisite rather than a minor gap.
- Incomplete or outdated business information on the profile itself at the time of review.
- Missing or incorrect Project Number in the submitted request.
- Assuming approval from an enabled API instead of checking the actual quota value, then debugging a phantom integration issue that is really a pending access request.
What Approved Access Unlocks — and Where It Connects to OAuth Review
Once a project is approved, the Business Profile APIs cover account and location management, review responses, Posts, business information updates, and location insights — all authenticated through the same OAuth 2.0 layer this site already covers for Google OAuth verification. For SaaS platforms managing multiple client profiles, the OAuth consent screen, scope justification, and business-verification steps run as a parallel track to the GBP access request itself, not a separate afterthought.
This is the same reason platforms working across Google’s developer surface — whether that is Business Profile management, YouTube Data API quota and compliance, or broader Google API and OAuth verification — tend to treat access approval as its own project phase, prepared and submitted correctly the first time rather than discovered through a string of quota errors.
An honest note. Google reviews every Business Profile API access request independently, and no outcome or timeline can be assured. What is covered here is the documented eligibility criteria and submission process as published by Google; the review decision itself always rests with Google.
Sources: Google for Developers — Business Profile APIs, Prerequisites (developers.google.com/my-business/content/prereqs), Implement OAuth with Business Profile APIs (developers.google.com/my-business/content/implement-oauth). Reviewed August 2026. Google’s documentation changes; verify against the current pages before acting. Not affiliated with or endorsed by Google LLC.