Google Business Profile management - #22
Merged
Merged
Conversation
A google_business resource covering the profile, attributes, food menus, services, photos, place action links, verification, performance and search keywords, plus assign, which hands the location to another workspace. Responses relay Google's own shape as plain dicts rather than models we would have to keep chasing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Google Business Profile management surface to this client, matching the
routes added in
fopost(/v1/accounts/:id/gbp/...).What it covers: the location profile, attributes, food menus, services,
photos, place action links, verification, and performance (daily impressions,
calls, direction requests, website clicks, plus the monthly search terms),
along with handing a location to another workspace.
Shape: responses relay Google's own payload field for field, so they come
back untyped rather than as models that would need chasing every time Google
adds a field. Requests are the API's snake_case names.
Gating: Google grants Business Profile API access per project. Until that
grant lands on a deployment every call answers
503 configuration_error.Covered by tests: one case per route asserting the URL and body actually sent,
plus the pending-grant refusal.