Google and Facebook connections
The Google and Facebook sign-in flow, completed when a business owner authorizes response posting.
What happens when a business owner authorizes response posting on Google or Facebook, and the calls that make it work.
Google and Facebook authorize posting through their own sign-in. The owner clicks a link (from Connect review sites, "Send the business owner a connection link"), signs in on Google's or Facebook's page, and grants access. These endpoints are what your connection page calls to complete that round trip and to disconnect later.
If you use our branded connection page, you don't call these yourself; the page does. They're documented so you know what's happening and can handle disconnects. Building the authorization step into your own app is not offered today; use the connection link.
Prerequisites
- A bearer token in the
Authorizationheader. Any endpoint that needs no token says so on its own page. - The id of each record the call targets. Every endpoint page lists the ids it needs.
Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Individual endpoints may return more; each page lists its own.
Endpoints
GET — Exchange the code Google returns after the owner signs in for the access needed to post on their behalf.
POST — Attach a location to the specific Google Business Profile the owner chose.
POST — Attach a location to the Facebook page the owner chose.
Updated 19 days ago
