Google Business Posting API
Through a single POST request, the Google Business Posting API enables a product, automation, agency workflow, or AI system to publish Google Business Profile updates.
POST {{API_BASE_URL}}/v1/posts
x-access-key: YOUR_API_KEY
Content-Type: application/json
{
"content": "A short example update.",
"platforms": [
{
"platform": "googlebusiness",
"accountId": "gbp_123",
"platformSpecificData": {
"topicType": "STANDARD",
"callToActionType": "LEARN_MORE",
"callToActionUrl": "https://example.com/hours"
}
}
],
"publishNow": true
}POST {{API_BASE_URL}}/v1/posts
x-access-key: YOUR_API_KEY
Content-Type: application/json
STANDARD, EVENT, and OFFER are the supported post types; photos are attached via mediaItems, buttons are configured via platformSpecificData, a specific connected account is selected via accountId, and future publication is controlled via scheduledFor and timezone. Google Business Profile is the current name for the service formerly called Google My Business, so the Google My Business API name refers to the same ecosystem.
What the Google Business Posting API does and who it is for
Choose this API when a product needs to publish to Google Business Profile locations programmatically and does not want to maintain a separate platform integration for every workflow. Developers, SaaS teams, agencies, automation builders, and AI products that need to publish updates, events, and offers from the same endpoint used for other social platforms are the intended audience. In practice, you connect a Google Business account, note its accountId, send a POST request to /v1/posts containing content and a googlebusiness platform target, and then check the returned status together with the per-platform success value.
Exact endpoint and Standard worked example
Direct the request to POST {{API_BASE_URL}}/v1/posts. In the captured Standard example, content holds the update text, the googlebusiness target carries accountId gbp_123, platformSpecificData.topicType is STANDARD, callToActionType is LEARN_MORE with callToActionUrl https://example.com/hours, and publishNow is true. The captured response uses HTTP 202 and contains success true, status published, postId post_abc123, and a platforms array with platform googlebusiness and success true. Use those values as the exact worked example, and after each request check success, status, postId, and the per-platform success flag instead of assuming delivery from the request alone.
Field map
Assemble each request from the captured field map. Top-level content carries the post text. The platforms array holds one target per destination; for Google Business, that target sets platform to googlebusiness and uses accountId to select the connected integration. Within platformSpecificData, topicType chooses STANDARD, EVENT, or OFFER, while callToActionType and callToActionUrl configure the button. Attach a photo via mediaItems using a public image URL, use publishNow for immediate publication as shown in the captured example, and use scheduledFor with timezone for future publication. Where requiredness, type, or exact location is not evidenced in the captured contract, validate against the full reference before implementation.
Format guide: Standard, Photo, Event, Offer, and Cross-Post
For a Standard post, set topicType to STANDARD for a regular location update and add a photo or call-to-action button where needed. For a Photo post, attach the image through mediaItems using a public image URL. For an Event post, set the post type through platformSpecificData and provide the event title, start date, end date, and times described in the source. For an Offer post, set the post type through platformSpecificData and provide coupon code, terms, and online redemption URL details described in the source. For Cross-Post, include Google Business and other platform targets in the same platforms array so the same update is sent in a single request. Product Posts are not currently supported, so do not use this endpoint for that format.
Response and success checking
Judge success from the response rather than the request. The captured Standard response uses success true, status published, postId post_abc123, and platforms[0].success true for googlebusiness. When cross-posting, inspect each platform entry separately because one destination succeeding does not prove another destination succeeded. If a platform entry reports failure, record the postId, the failing platform, and the exact request fields used so the failure can be reproduced and corrected.
Scheduling, cross-posting, and direct integration versus a unified endpoint
Scheduling uses scheduledFor and timezone to queue a Google Business update for a future date and time. Set the timezone explicitly so the intended local publication time is unambiguous, and confirm the scheduled value before relying on it. Cross-platform publishing uses the same endpoint by adding additional platform targets to the platforms array, which keeps content, timing, and success checking in one workflow. A direct Google Business Profile API integration gives you platform-specific control but requires you to handle authentication, account connections, tokens, payloads, validation, and publishing logic yourself, whereas a unified endpoint centralizes those concerns and lets the same /v1/posts workflow serve Google Business and other social platforms.
Request builder checklist and failure checks
Before sending, run a short checklist. Confirm the accountId belongs to the intended connected Google Business integration. Confirm topicType is one of STANDARD, EVENT, or OFFER. Confirm callToActionType is a supported value such as LEARN_MORE and that callToActionUrl is present where the button requires a destination. Confirm any mediaItems entry uses a public image URL. Confirm scheduledFor and timezone are both set for scheduled posts and that the timezone matches the intended local time. After sending, confirm the response success value, status, postId, and per-platform success entry, and investigate any target that did not succeed before retrying.
| Field | Location | Captured value or enum | Use |
|---|---|---|---|
| content | Top level | Example text in captured request | Post text |
| platforms[].platform | Platform target | googlebusiness | Selects Google Business destination |
| platforms[].accountId | Platform target | Example: gbp_123 | Chooses the connected Google Business integration |
| platforms[].platformSpecificData.topicType | Platform target | STANDARD | EVENT | OFFER | Selects post type |
| platforms[].platformSpecificData.callToActionType | Platform target | LEARN_MORE in example; Book, Order, Shop, Learn More, Sign Up, Call, Get Offer described | Selects call-to-action button |
| platforms[].platformSpecificData.callToActionUrl | Platform target | Example: https://example.com/hours | Button destination URL where required |
| mediaItems | Not evidenced in captured contract | Public image URL described | Attaches a photo |
| publishNow | Top level | true in captured example | Immediate publication in captured example |
| scheduledFor | Not evidenced in captured contract | Future date/time described | Scheduling |
| timezone | Not evidenced in captured contract | Timezone described | Scheduling timezone |
Requiredness, types, and exact location are only as evidenced in the captured example and prose; validate the full reference before implementation. Location for scheduledFor, timezone, and mediaItems is not evidenced in the captured contract.
| Failure or unsupported case | Check | Corrective action |
|---|---|---|
| Product Post requested | topicType is not STANDARD, EVENT, or OFFER for Product Posts | Do not claim support; Product Posts are not currently supported |
| Missing or wrong accountId | accountId does not match the intended connected integration | Pass the correct accountId for the target location |
| Unsupported callToActionType | Value is outside the supported CTA set | Use a supported CTA type and set callToActionUrl where required |
| Photo not attached | mediaItems missing or image URL is not public | Provide mediaItems with a public image URL |
| Scheduling misuse | scheduledFor or timezone missing or inconsistent | Set both fields and verify the intended local time |
| Partial cross-post failure | One platforms entry has success false | Inspect each per-platform success value and retry only the failed target after correction |
Error response bodies and status codes beyond the captured 202 Standard example are not evidenced.
Frequently asked questions
What can I publish with the Google Business Posting API?
Three topic types are documented: STANDARD covers ordinary location updates, EVENT covers scheduled events, and OFFER covers promotions. A photo can be supplied via mediaItems, and a supported button can be configured alongside the post.
Is the Google My Business API the same as the Google Business Profile API?
Google Business Profile is the newer name for the service previously called Google My Business. References to the Google My Business API or GMB API generally describe that same ecosystem.
Why use a unified endpoint instead of integrating with the Google Business Profile API directly?
With a unified endpoint, sign-in, account linking, token handling, payload construction, validation, and delivery are centralized, allowing one /v1/posts workflow to cover Google Business alongside other networks. Going direct offers platform-specific control, but you must implement and maintain each of those responsibilities yourself.
Do I need to create my own Google Cloud project?
No. Because the unified integration already manages the Google Business connection, this posting workflow does not require you to set up a separate Google Cloud project or write your own API implementation for it.
Which Google Business post types does the Google Business Posting API support?
STANDARD is for ordinary updates, EVENT is for events, and OFFER is for promotions.
Can I create Google Business Product Posts through the API?
They are not supported at present. Only STANDARD, EVENT, and OFFER are documented.
Can I add a call-to-action button to a Google Business post?
Yes. Available choices are Book, Order, Shop, Learn More, Sign Up, Call, and Get Offer. Specify the choice in callToActionType and, when the button needs one, supply its destination in callToActionUrl.
Can I schedule Google Business Profile posts?
Set scheduledFor together with timezone so the update goes out at a chosen future date and time. Verify both values before sending; the captured contract does not establish how they interact with publishNow.
How do I know whether my Google Business post was published successfully?
Inspect success, status, postId, and the success flag for the individual platform in the response. In the captured Standard example, the service answers with HTTP 202, status published, and a true per-platform success value. Webhooks may also deliver status updates.
Who is the Google Business Posting API for?
It suits developers, SaaS teams, agencies, automation builders, and AI products that require programmatic social publishing.
{
"success": true,
"status": "published",
"postId": "post_abc123",
"platforms": [
{
"platform": "googlebusiness",
"success": true
}
]
}