Google Business Profile API
Use this guide to configure the connection safely, then verify the account and permissions before you publish or automate.
Use this guide
- Prepare the provider credentials and callback values required for this connection.
- Enter them in the related settings area, save, and connect one safe test account.
- Verify the returned name, status, and permissions before using the connection.
Detailed steps
📌 Google Business Profile (GBP) API Integration – Stackposts (Updated 2026)
1️⃣ Overview
Google Business Profile (GBP) API integration allows Stackposts to connect with and manage verified Google Business Profiles owned or authorized by users.
Once approved and configured, users can:
-
Publish Google Business Profile posts (user-initiated)
-
Upload images
-
Manage verified business locations
-
Work with multiple authorized locations
⚠️ Important
Access to the GBP API requires manual approval by Google.
Correct configuration does not guarantee approval.
2️⃣ Supported Features
| Feature | Status |
|---|---|
| Publish GBP posts | ✅ |
| Upload images | ✅ |
| Multiple locations | ✅ |
| Analytics / Insights | ❌ |
| Automated / bulk posting | ❌ (Not allowed by Google) |
3️⃣ Configuration Fields (Stackposts)
| Field | Description |
|---|---|
| Status | Enable / Disable GBP integration |
| Client ID | OAuth 2.0 Client ID |
| Client Secret | OAuth Client Secret |
| API Key | Optional (not required for posting) |
4️⃣ OAuth Redirect URI (Callback URL)
Add the following exact URL to Authorized Redirect URIs in Google Cloud Console:
⚠️ Must match exactly (protocol, domain, path).
5️⃣ Google Cloud Console Setup
Step 1: Create Project
-
Go to Google Cloud Console
-
Create or select a project
Step 2: Enable API
Enable Google My Business API
❌ Do NOT enable “Business Profile API” (deprecated / not used)
Step 3: OAuth Consent Screen
-
User type: External
-
App name: Your platform name
-
Authorized domains: yourdomain.com
-
Scopes: required by Stackposts
-
Status: Published (Production)
6️⃣ 🧾 Requesting API Access Approval (REQUIRED)
⚠️ This step is mandatory. Without approval, the API quota remains 0 and Stackposts will not work.
By default, new Google projects have:
Any API call will return:
🔗 Official Access Request Form
👉 Google Business Profile API Access Request Form
(Official Google form)
🔎 How to find Project Number
-
Open Google Cloud Console
-
Go to Project Dashboard
-
Copy Project Number (not Project ID)
📝 Form Fields – What to Submit
| Field | What to Enter |
|---|---|
| Access Type | Basic Access Request |
| Project Number | Your Google Cloud project number |
| Business Name | Your verified Google Business Profile |
| Business Website | Your official website |
| Contact Email | Email that manages the GBP |
✅ Recommended Use-Case Description (Updated)
Use this or adapt it carefully:
Our platform is an internal business management system used by verified business owners and authorized staff to manage their own Google Business Profiles.
The Google Business Profile API is used to:
Publish posts manually initiated by users
Upload user-selected media
Update business information for verified locations
Manage multiple locations owned or authorized by the same business
All actions are initiated directly by users.
The platform does not perform automated, spam, scraping, or bulk posting.
🚫 Avoid words like: automation, bulk, AI posting, mass posting, marketing bot
⏳ Review Timeline
-
Typical review time: 3–7 business days
-
In some cases: 1–3 weeks
-
You will receive an email from the Google Business Profile API Team
If approved:
-
Quota increases (usually 300 QPM)
-
Stackposts GBP integration will work normally
7️⃣ Mandatory Website Requirements (Google Checks)
Required
-
Privacy Policy (must mention Google data usage)
-
Terms of Service
-
Contact page (real email + address)
-
About / Company page
-
Data deletion & account removal instructions
Strongly Recommended
-
A dedicated page: “Google Business Profile Integration” explaining:
-
What data is accessed
-
User-initiated actions
-
Ownership / authorization requirements
-
Compliance with Google policies
-
8️⃣ Common Rejection Reasons
| Reason | Explanation |
|---|---|
| Internal quality checks failed | Website trust / transparency |
| Automation wording | Disallowed SaaS positioning |
| Missing legal pages | Privacy / Terms incomplete |
| OAuth not verified | Consent screen still in testing |
| Generic marketing site | No clear GBP use explanation |
9️⃣ Common Errors & Fixes
| Error | Cause | Solution |
|---|---|---|
| Quota exceeded (0 QPM) | Not approved | Submit access request |
| invalid_redirect_uri | Callback mismatch | Fix redirect URI |
| unauthorized_client | OAuth not published | Publish consent screen |
| access_denied | Missing scopes | Reconnect account |
🔟 Important Notes
-
GBP API approval is not guaranteed
-
Stackposts cannot influence approval
-
Each platform must apply independently
-
Google reviews SaaS tools very strictly
11️⃣ Disclaimer
Stackposts provides technical integration only.
API approval, quota limits, and compliance are controlled entirely by Google.
Quick check
- The save or publish action completes without an error.
- The visible status, preview, or connected account matches the change.
- If the result differs, capture the exact message and review the troubleshooting guidance before retrying.