The Google Business API,without the access request

No. The location connects through OmniSocials’ Google connection, with Google’s own sign-in. You call the OmniSocials API with an API key and never handle Google’s tokens, which expire every hour.

Any location your Google account manages, in every account it can reach. Right after you sign in with Google you pick the location; with only one, OmniSocials picks it for you. A Google account without a location can’t be connected.

Each workspace posts to one location. A second location goes in a second workspace, with its own key.

Not yet. Locations connect inside the OmniSocials app. Every API key in that workspace can then post to the location.

Updates, events and offers, Google’s own three. Each post takes text and one image, or no image. An event adds a title with a start and an end; an offer adds a title, its dates, a coupon code or a redeem link, and terms.

Google Business takes no video and no second image.

Learn more, Book, Order online, Buy, Sign up or Call now, on any post type: cta.actionType is LEARN_MORE, BOOK, ORDER, SHOP, SIGN_UP or CALL. Every button except Call now needs a url. Call now uses the phone number on your Business Profile.

Google turns down a post with a phone number or a link in the text, with a bare 400 that doesn’t say why. OmniSocials checks the caption first and answers 400 validation_error with what to change, before the post is saved. Put the link on the offer or a button, and use Call now for your number.

Not per post. Google discontinued per-post insights for Business Profiles in 2023, so GET /v1/analytics/posts/:id answers metrics_unavailable: true with a note, never zeros.

GET /v1/analytics/accounts returns the location’s numbers per day and over 30 days: views on Search and Maps, on desktop and mobile, calls, direction requests, website clicks, bookings, rating and review count, and once a month the search keywords that showed your profile. Google reports them up to three days late.

No. Google reviews aren’t in the Social Inbox. The API reads the average rating and the number of reviews, as part of the location’s numbers.

On a temporary error, OmniSocials retries it up to 3 times, 15 minutes apart. When Google can’t fetch the image, OmniSocials warms it up and tries once more a few seconds later. Then post.published or post.failed fires.

Register a URL and pick the events: post.scheduled, post.published, post.failed, post.approved and post.rejected. Every delivery is signed with HMAC-SHA256 in the X-OmniSocials-Signature header.

Google doesn’t charge for it, but you have to request API access for a Google Cloud project and wait for Google to approve it. Through OmniSocials you skip the request, and the API is part of the plan, $10 per seat per month billed annually.

100 requests a minute per API key. Past that the API answers 429 with a Retry-After header that says when to try again.

One plan with every feature included: $10 per seat per month billed annually, or $12 billed monthly. Team members and client seats cost the same. Every account starts with a 14-day free trial.

The REST API, the SDKs, the CLI, webhooks and the MCP server are part of that one plan.