Google Business Scheduling API
The Google Business Scheduling API queues a Google Business Profile update for a later local moment rather than sending it at once.
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": "gb_123",
"platformSpecificData": {
"topicType": "STANDARD",
"callToActionType": "LEARN_MORE",
"callToActionUrl": "https://example.com/summer-hours"
}
}
],
"scheduledFor": "2026-09-15T09:00:00",
"timezone": "America/Chicago"
}
// 202 Response
{
"success": true,
"status": "scheduled",
"postId": "post_xyz789",
"scheduledFor": "2026-09-15T14:00:00.000Z",
"platforms": [
{
"platform": "googlebusiness",
"success": true
}
]
}POST {{API_BASE_URL}}/v1/posts
x-access-key: YOUR_API_KEY
Content-Type: application/json
One call carries the text, a googlebusiness target, an accountId, a scheduledFor timestamp, and a timezone; the reply supplies a postId plus scheduledFor in UTC for calendar display and later lifecycle handling.
What the Google Business Scheduling API Does
A product, agency workflow, automation, or AI system can hand Google Business Profile publishing to this API and skip operating its own queue. Updates can be held for a later moment, timed with IANA timezone support so each location receives them at its local hour, and released at an exact time rather than inside a loose window. Developers, SaaS teams, agencies, automation builders, and AI products needing programmatic scheduling are the intended users.
Create a Scheduled Update
Send POST {{API_BASE_URL}}/v1/posts carrying content, a platforms array, scheduledFor, and timezone. Inside platforms, platform is googlebusiness and accountId identifies the connected Google Business integration. Settings specific to Google Business sit under platformSpecificData, namely topicType, callToActionType, and callToActionUrl. Presence of scheduledFor changes behaviour: the item waits in queue until that moment instead of going out straight away. The example titled Schedule a Standard Update with Local Time shows the request and its 202 reply, containing success, status scheduled, postId, scheduledFor in UTC, and per-platform success.
Timezone Handling: Local Input, UTC Response
Alongside scheduledFor, pass an IANA timezone such as America/Chicago. The service converts that local moment and hands back the equivalent UTC publishing time. In the sample, 2026-09-15T09:00:00 in America/Chicago comes back as 2026-09-15T14:00:00.000Z. Omitting timezone makes scheduledFor count as UTC. Checks worth running: confirm the timezone string is a valid IANA name, decide whether the input was meant as local or UTC, and compare request and response values before showing a time to end users. No error contract for an invalid timezone or a past scheduledFor appears in the source, so verify those cases in the API reference instead of guessing.
Post Types, Targeting, and Call-to-Action Rules
Point accountId at the integration ID belonging to the connected Google Business account. topicType decides the kind of item: a standard update, an event, or an offer. The sample sets topicType to STANDARD, callToActionType to LEARN_MORE, and provides callToActionUrl. Actions on offer are Book, Order, Shop, Learn More, Sign Up, Call, and Get Offer; Call is the sole action that does not need a URL. Events pair a title with beginning and ending dates and times, while offers may pair a coupon code with an online redemption URL and terms and conditions. Pick STANDARD for a general announcement, EVENT for something bounded by start and end, and OFFER when a coupon, redemption link, or terms apply. Exact field names for event and offer details do not appear in the sample and need confirmation before implementation.
Calendar, Reschedule, Edit, and Cancel
A calendar can be built by creating each update with its own scheduledFor, weeks ahead if needed, and then listing scheduled posts for display. Queued items can be edited, shifted to a new moment, or cancelled ahead of publication, without rebuilding the content. Prose in the source mentions a reschedule endpoint, yet gives no method, path, parameters, or status contract; likewise no list or edit endpoint contract is given. Treat those lifecycle operations as stated capabilities whose exact contracts require verification in the API reference. Timing matters here: cancellation is described for the period before publication, so do not assume it remains available afterwards.
Cross-Platform Queuing
One request can carry Google Business alongside other supported platforms when the content suits each. All targets in that request share a single scheduledFor and timezone, giving a campaign one publishing moment and one timezone conversion. Check every target's accountId before sending, since a single call queues identical content to several profiles at once. The reply's per-platform success flags show which targets were accepted.
| Field | Type | Required | Value / Rule |
|---|---|---|---|
| content | string | Shown in example | Post text, e.g. Summer hours announcement |
| platforms[].platform | string | Shown in example | googlebusiness |
| platforms[].accountId | string | Shown in example | Integration ID for the connected Google Business account, e.g. gb_123 |
| platforms[].platformSpecificData.topicType | string | Shown in example | STANDARD in example; standard updates, events, and offers are supported types |
| platforms[].platformSpecificData.callToActionType | string | Shown in example | LEARN_MORE in example; Book, Order, Shop, Learn More, Sign Up, Call, Get Offer |
| platforms[].platformSpecificData.callToActionUrl | string | Required except Call | URL for CTA types other than Call, e.g. https://example.com/summer-hours |
| scheduledFor | string (ISO 8601) | Shown in example | Local scheduled time when timezone is supplied, e.g. 2026-09-15T09:00:00 |
| timezone | string (IANA) | Optional | e.g. America/Chicago; if omitted, scheduledFor is treated as UTC |
| Event fields (title, start/end dates and times) | Not specified in example | Gap | FAQ describes contents only; exact field names not evidenced |
| Offer fields (coupon code, redemption URL, terms) | Not specified in example | Gap | FAQ describes contents only; exact field names not evidenced |
Exactly as evidenced in the supplied Standard Update example and FAQ; unspecified fields are marked as gaps rather than invented.
| Field | Type | Value / Rule |
|---|---|---|
| success | boolean | true |
| status | string | scheduled |
| postId | string | e.g. post_xyz789 |
| scheduledFor | string (UTC) | Resolved UTC publishing time, e.g. 2026-09-15T14:00:00.000Z |
| platforms[].platform | string | googlebusiness |
| platforms[].success | boolean | true |
202 response exactly as shown in the supplied example.
| Post Type | Use When | Contents |
|---|---|---|
| STANDARD | General announcement or update | Content plus optional call-to-action |
| EVENT | Time-bound event | Title plus start and end dates and times |
| OFFER | Promotion with redemption terms | Coupon code, online redemption URL, terms and conditions |
Decision criteria derived from FAQ contents; exact EVENT/OFFER field contracts are gaps.
Frequently asked questions
How do I schedule a Google Business update?
POST to /v1/posts, naming the connected profile through accountId and supplying an ISO 8601 value in scheduledFor. Include an IANA timezone when the moment is meant in local terms. Acceptance returns status scheduled, a postId, and scheduledFor resolved in UTC.
How does timezone handling work?
Supply an IANA timezone, for example America/Chicago. Leaving timezone out means scheduledFor is read as UTC. The reply carries the resolved moment in UTC, so check that value against the local input before presenting either one in a calendar.
What types of Google Business posts can I schedule?
Three kinds are available: standard updates, events, and offers. topicType selects among them, and the worked example exercises STANDARD. Names for the extra event and offer fields are not shown in that example.
How do I target the correct Google Business Profile?
Put the connected account's integration ID into accountId inside the platforms array. The sample pairs platform googlebusiness with accountId gb_123. Confirm that identifier points at the intended profile before depending on delivery.
What call-to-action buttons can I use?
Available actions are Book, Order, Shop, Learn More, Sign Up, Call, and Get Offer. Every action except Call needs a URL, passed as callToActionUrl; the sample pairs LEARN_MORE with a URL.
What can I include in an event or offer?
An event carries a title together with beginning and ending dates and times. An offer may carry a coupon code, a redemption URL for online use, and terms and conditions. The sample request does not reveal the exact field names for those details.
Can I edit, reschedule, or cancel a scheduled Google Business update?
While an item is still queued, it can be edited, shifted to another moment, or cancelled ahead of publication. The source prose mentions a reschedule endpoint without giving its method, path, parameters, or status contract, so confirm those from the API reference first.
Who is the Google Business Scheduling API for?
Developers, SaaS teams, agencies, automation builders, and AI products that need programmatic scheduling for Google Business Profile updates, without operating a publishing queue themselves.