Skip to main content

Google Business Posts

Everything Google's Business Profile API lets you do with a location's posts ("Updates" tab). Posts are created with the normal upload endpoints (text, photo, video) with platform[]=google_business, edited with Edit post and deleted with Unpublish. This page covers reading posts and the extra post options.

  • Authentication: API Key — Authorization: Apikey <YOUR_API_KEY>
  • No reconnection is needed: the Google Business connection already has the business.manage permission.

List posts​

  • Method: GET
  • Endpoint: /api/uploadposts/google-business/posts
ParameterTypeRequiredDescription
userstringYesProfile username with Google Business connected.
location_idstringNolocations/123, 123 or accounts/456/locations/123. Same rules as Location Info ("Which location?").
page_sizeintegerNo1-100. Default 20 (Google's default).
page_tokenstringNonext_page_token from the previous page.
curl 'https://api.upload-post.com/api/uploadposts/google-business/posts?user=my-shop&page_size=50' \
-H 'Authorization: Apikey YOUR_API_KEY'
{
"success": true,
"location_id": "locations/111",
"account": "accounts/9",
"count": 1,
"posts": [
{
"name": "accounts/9/locations/111/localPosts/55",
"topicType": "EVENT",
"summary": "Live music every Friday",
"state": "RECURRING",
"searchUrl": "https://local.google.com/place?...",
"event": { "title": "Friday gigs", "schedule": { "...": "..." },
"recurrenceInfo": { "weeklyPattern": { "daysOfWeek": ["FRIDAY"] } } }
}
],
"next_page_token": null
}

Each item is Google's LocalPost as Google returns it.

Read one post​

  • Method: GET
  • Endpoint: /api/uploadposts/google-business/posts/get
ParameterTypeRequiredDescription
userstringYesProfile username.
post_idstringYesFull post name returned on upload or by the list: accounts/{a}/locations/{l}/localPosts/{p}.
{
"success": true,
"post_id": "accounts/9/locations/111/localPosts/55",
"state": "LIVE",
"post": { "name": "accounts/9/locations/111/localPosts/55", "state": "LIVE", "...": "..." }
}

Post states​

stateMeaning
PROCESSINGGoogle is reviewing the post; it is not visible yet. Almost every new post starts here.
LIVEPublished and visible on Google.
SCHEDULEDScheduled with gbp_scheduled_time; Google publishes it later.
RECURRINGA recurring post that is currently visible.
REJECTEDGoogle rejected it for a content policy violation. It is not visible.

The list and the read above always show Google's current state. In the upload result, only a post scheduled with gbp_scheduled_time carries state: SCHEDULED for now.

Not generally available yet

Post-state tracking is not generally available yet. Once it is enabled, the upload result carries Google's state and Upload-Post reads posts that come back PROCESSING (or SCHEDULED) again later; if Google rejects one, the post turns into a failure in Upload Status and history with error_code: content_rejected. Until then, check a post with Read one post.

Extra options when creating a post​

Send these with the upload request, next to the other gbp_* fields. Requests that do not send them behave exactly as before. They are checked when the request is accepted, also for posts scheduled with scheduled_date: a mistake answers 400 (or 503 gbp_feature_disabled if the option is temporarily off) right away when Google Business is the only network of the request. When the request also publishes on other networks, it goes on: only the Google Business part fails, with the same error_code.

Recurring posts (EVENT and OFFER)​

FieldDescription
gbp_recurrenceDAILY, WEEKLY or MONTHLY.
gbp_recurrence_daysWEEKLY only. Days, comma separated or repeated (gbp_recurrence_days[]): MONDAY…SUNDAY or MON…SUN. Empty = the weekday of the event start.
gbp_recurrence_day_of_monthMONTHLY: day of the month, 1-31.
gbp_recurrence_week_occurrenceMONTHLY: FIRST, SECOND, THIRD, FOURTH or LAST (the weekday is the one of the event start: an event on a Friday with SECOND repeats every second Friday). Send this or gbp_recurrence_day_of_month, not both.
gbp_recurrence_endEnd of the series: YYYY-MM-DD (end of that day, UTC) or an RFC 3339 timestamp. On or after the event end and at most one year after the event start. Without it the series ends one year after the event start (returned as recurrence_end).

A recurring post needs gbp_event_start_date and gbp_event_end_date (the first occurrence), starting within a year. Missing times become the whole day (00:00 to 23:59), because Google needs every field of the interval. An occurrence cannot last longer than its pattern repeats: one day for DAILY, up to 7 days for WEEKLY, up to 28 days for MONTHLY.

curl -X POST https://api.upload-post.com/api/upload_text \
-H 'Authorization: Apikey YOUR_API_KEY' \
-F 'user=my-shop' -F 'platform[]=google_business' \
-F 'title=Live music every Friday' \
-F 'gbp_topic_type=EVENT' -F 'gbp_event_title=Friday gigs' \
-F 'gbp_event_start_date=2026-12-04' -F 'gbp_event_start_time=20:00' \
-F 'gbp_event_end_date=2026-12-04' -F 'gbp_event_end_time=23:00' \
-F 'gbp_recurrence=WEEKLY' -F 'gbp_recurrence_days=FRIDAY' -F 'gbp_recurrence_end=2027-03-31'

Errors (400, nothing is sent to Google): INVALID_RECURRENCE with a message that says which field is wrong.

Google's native scheduling​

FieldDescription
gbp_scheduled_timeRFC 3339 timestamp with time zone, e.g. 2026-12-01T09:00:00+01:00, at most one year ahead. Google receives the post now and publishes it at that time (state: SCHEDULED).

Upload-Post's own scheduling (scheduled_date) is still the default and the recommended option. Use gbp_scheduled_time only if you want the post to sit in Google's own queue:

  • Once Google has it, cancelling or editing the scheduled post in Upload-Post does nothing. Delete it with Unpublish or change the time with Edit post (scheduled_time).
  • If you combine it with scheduled_date, it must be later than scheduled_date (400 INVALID_SCHEDULED_TIME otherwise).
  • If the time has already passed when the post is sent (for example a retry), the post is published right away and the result carries a warning.
  • If Google's scheduling is temporarily off when a post with a future gbp_scheduled_time is sent, the post is not published early: the Google Business part fails with 503 gbp_feature_disabled and the other networks go on.
  • The upload result carries scheduled_time, url: null (the post is not visible yet) and scheduled_url.

Several photos or videos in one post​

FieldDescription
gbp_multi_mediatrue to send every attached photo, or every gbp_media_url[], to Google. Without it only the first one is sent, as before.
gbp_media_url[]Public URLs (repeat the field or send a JSON array). When given, attached photos are not sent to Google Business (the result says so in warnings).

Photos only, up to 10 per post, from /api/upload_photos or /api/upload_text. A video always goes alone (400 MULTI_MEDIA_PHOTOS_ONLY). Google does not publish a maximum and may refuse several media on some locations; if that happens, publish one. Errors: TOO_MANY_MEDIA, INVALID_MEDIA_URL, MEDIA_TOO_SMALL, MEDIA_LIMITS (400). The result carries media_count. ALERT posts never carry media.

These options are for posts only: on a gallery upload (gbp_post_type=MEDIA) they answer 400 NOT_SUPPORTED_FOR_GALLERY.

Editing posts​

Not generally available yet

Editing the media, the Google publish time and the recurrence of a post is not generally available yet. Until then these fields are ignored, as before.

Edit post with platform: google_business takes, besides summary, the call to action, event and offer fields:

FieldDescription
media_urlA public URL, a JSON list or the field repeated (max 10; several = photos only). A URL is never split on commas. Replaces the post's media. media_format (PHOTO or VIDEO) optional; detected from the URL otherwise.
scheduled_timeNew Google publish time (RFC 3339 with time zone, in the future, at most a year ahead).
recurrence, recurrence_days, recurrence_day_of_month, recurrence_week_occurrence, recurrence_endReplace the recurrence of an EVENT or OFFER post (same values as above; recurrence_end is required here).

The gbp_ spellings (gbp_scheduled_time, gbp_recurrence…) are accepted too. Errors carry error_code (INVALID_MEDIA_URL, TOO_MANY_MEDIA, INVALID_MEDIA_FORMAT, INVALID_SCHEDULED_TIME, INVALID_RECURRENCE).

Errors​

Errors carry success: false, code and error_code (same value) and an error message:

  • 400 invalid_page_size, invalid_page_token, invalid_post_id, location_required.
  • 404 post_not_found, location_not_found.
  • 401 google_business_reconnect_required, 403 google_business_permission_denied.
  • 429 google_rate_limited (Google is limiting the account, or too many reads this minute; retry_after_seconds says when to retry), 429 daily_limit_reached (a daily limit of reads; scope says which one, daily_limit the limit and retry_after_seconds when it resets) and 429 google_daily_quota_exhausted (Google's own daily quota is used up).
  • 502 google_result_unknown on edit or unpublish (and error_code: google_result_unknown in an upload result): Google did not confirm the change and it may have been applied. Check before trying again.
  • 503 gbp_feature_disabled: the feature is temporarily switched off.

Limits​

Google's per-minute quota for each API is shared by the whole platform. Reads (/posts, /posts/get) have a per-minute and a daily limit per account; publishing is never blocked by them.